Vulnerability-Lookup

CVE-2026-49831 (GCVE-0-2026-49831)

Vulnerability from cvelistv5 – Published: 2026-09-02 17:17 – Updated: 2026-09-02 19:01

Title

DSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability)

Summary

DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.7, 8.4, 9.3, and 10.0, the Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often 'tomcat') user is allowed. This constitutes a Path Traversal Vulnerability in the curate script. This issue has been patched in versions 7.6.7, 8.4, 9.3, and 10.0.

Severity

5.5 (Medium)


                        
                          CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H

SSVC

Exploitation: none Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-09-02 19:01 UTC

CWE

CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Assigner

GitHub_M mitre root

References

4 references

URL	Tags
https://github.com/DSpace/DSpace/security/advisor…	x_refsource_CONFIRM
https://github.com/DSpace/DSpace/pull/12539	x_refsource_MISC
https://github.com/DSpace/DSpace/pull/12540	x_refsource_MISC
https://github.com/DSpace/DSpace/pull/12552	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version	CPE status
DSpace	DSpace	Affected: < 7.6.7 Affected: >= 8.0-rc1, < 8.4 Affected: >= 9.0-rc1, < 9.3 Affected: = 10-rc1	guessed

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-49831",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-02T19:01:23.911474Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-02T19:01:29.463Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "DSpace",
          "vendor": "DSpace",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 7.6.7"
            },
            {
              "status": "affected",
              "version": "\u003e= 8.0-rc1, \u003c 8.4"
            },
            {
              "status": "affected",
              "version": "\u003e= 9.0-rc1, \u003c 9.3"
            },
            {
              "status": "affected",
              "version": "= 10-rc1"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.7, 8.4, 9.3, and 10.0, the Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often \u0027tomcat\u0027) user is allowed. This constitutes a Path Traversal Vulnerability in the curate script. This issue has been patched in versions 7.6.7, 8.4, 9.3, and 10.0."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 5.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "HIGH",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-22",
              "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-02T17:17:29.261Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5"
        },
        {
          "name": "https://github.com/DSpace/DSpace/pull/12539",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/DSpace/DSpace/pull/12539"
        },
        {
          "name": "https://github.com/DSpace/DSpace/pull/12540",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/DSpace/DSpace/pull/12540"
        },
        {
          "name": "https://github.com/DSpace/DSpace/pull/12552",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/DSpace/DSpace/pull/12552"
        }
      ],
      "source": {
        "advisory": "GHSA-v66x-68f2-pxf5",
        "discovery": "UNKNOWN"
      },
      "title": "DSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability)"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-49831",
    "datePublished": "2026-09-02T17:17:29.261Z",
    "dateReserved": "2026-06-01T18:50:36.056Z",
    "dateUpdated": "2026-09-02T19:01:29.463Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-49831",
      "date": "2026-09-04",
      "epss": "0.00348",
      "percentile": "0.27676"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-49831\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-09-02T18:19:32.683\",\"lastModified\":\"2026-09-02T19:17:19.100\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.7, 8.4, 9.3, and 10.0, the Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often \u0027tomcat\u0027) user is allowed. This constitutes a Path Traversal Vulnerability in the curate script. This issue has been patched in versions 7.6.7, 8.4, 9.3, and 10.0.\"}],\"affected\":[{\"source\":\"security-advisories@github.com\",\"affectedData\":[{\"vendor\":\"DSpace\",\"product\":\"DSpace\",\"versions\":[{\"version\":\"\u003c 7.6.7\",\"status\":\"affected\"},{\"version\":\"\u003e= 8.0-rc1, \u003c 8.4\",\"status\":\"affected\"},{\"version\":\"\u003e= 9.0-rc1, \u003c 9.3\",\"status\":\"affected\"},{\"version\":\"= 10-rc1\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"HIGH\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.2,\"impactScore\":4.2}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-09-02T19:01:23.911474Z\",\"id\":\"CVE-2026-49831\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-22\"}]}],\"references\":[{\"url\":\"https://github.com/DSpace/DSpace/pull/12539\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/DSpace/DSpace/pull/12540\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/DSpace/DSpace/pull/12552\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5\",\"source\":\"security-advisories@github.com\"}]}}"
  }
}

FKIE_CVE-2026-49831

Vulnerability from fkie_nvd - Published: 2026-09-02 18:19 - Updated: 2026-09-02 19:17

Severity

5.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H

Summary

References

	URL	Tags
	security-advisories@github.com	https://github.com/DSpace/DSpace/pull/12539
	security-advisories@github.com	https://github.com/DSpace/DSpace/pull/12540
	security-advisories@github.com	https://github.com/DSpace/DSpace/pull/12552
	security-advisories@github.com	https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "DSpace",
          "vendor": "DSpace",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 7.6.7"
            },
            {
              "status": "affected",
              "version": "\u003e= 8.0-rc1, \u003c 8.4"
            },
            {
              "status": "affected",
              "version": "\u003e= 9.0-rc1, \u003c 9.3"
            },
            {
              "status": "affected",
              "version": "= 10-rc1"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.7, 8.4, 9.3, and 10.0, the Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often \u0027tomcat\u0027) user is allowed. This constitutes a Path Traversal Vulnerability in the curate script. This issue has been patched in versions 7.6.7, 8.4, 9.3, and 10.0."
    }
  ],
  "id": "CVE-2026-49831",
  "lastModified": "2026-09-02T19:17:19.100",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 5.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.2,
        "impactScore": 4.2,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-49831",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-09-02T19:01:23.911474Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-09-02T18:19:32.683",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/DSpace/DSpace/pull/12539"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/DSpace/DSpace/pull/12540"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/DSpace/DSpace/pull/12552"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Received",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}

GHSA-V66X-68F2-PXF5

Vulnerability from github – Published: 2026-07-08 20:25 – Updated: 2026-07-08 20:25

Summary

DSpace has a possible Path Traversal Vulnerability in its Curation Task Reporter output path

Details

Overview

The Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often 'tomcat') user is allowed. This constitutes a Path Traversal Vulnerability in the curate script.

This was not a real problem when curation tasks could only be run from the command-line as a system administrator, but now that Collection/Community/Site Administrators can also run curation tasks via the web user interface, it introduces a possibility for an attacker with DSpace administrative credentials to set command parameters in such a way that output ends up in an unexpected location (for example, static resources folder in the Spring boot webapp, or overwriting a configuration file).

This vulnerability impacts DSpace versions <= 7.6.6, 8.0 <= 8.3, 9.0 <= 9.2. The attacker MUST already have DSpace Collection/Community/Site Administrator credentials in order to perform the attack.

Expected behaviour : Only a set of configured output directories should be allowed as base paths for Curation reporter output. The fix applied here is designed to be used with other systems that need to read or write streams on disk. In addition, we do not see a need for the web-managed processes to allow the -r reporter output parameter at all.

Impact

The ability to overwrite a file in /dspace/config or /dspace/bin is not desired, and could result in a denial of service attack. To actually use the curation reporter to perform an attack that escalates privileges, either a custom curation task would be needed (these can only be deployed by a system administrator), or the output would have to contain some executable information that is combined with other attacks, as a way to provide a payload in a local path.

Patches

The fix is included in DSpace 7.6.7, 8.4, 9.3 and 10.0. Please upgrade to one of these versions at the earliest convenience

If users cannot upgrade immediately, it is possible to manually patch their DSpace backend. (No changes are necessary to the frontend.) A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.x. * Pull request for 9.x: https://github.com/DSpace/DSpace/pull/12552 (Downloadable patch file) * This 9.x patch file also resolves a similar path traversal vulnerability in LDN messages * Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12540 (Downloadable patch file) * This 8.x patch file also resolves a similar path traversal vulnerability in LDN messages * Pull request for 7.x: https://github.com/DSpace/DSpace/pull/12539 (Downloadable patch file)

Apply the patch to a user's DSpace

If at all possible, DSpace maintainers recommend disabling the ORE Crosswalk (see below) or upgrading users' DSpace site based on the upgrade instructions. However, if usersare unable to do so, they can manually apply the above patches to their DSpace backend as follows: 1. Download the appropriate patch file to the machine where DSpace backend is running 2. From the [dspace-src] folder, apply the patch, e.g. git apply [name-of-file].patch 3. Now, update the DSpace site (based loosely on the Upgrade instructions). This generally involves three steps: 1. Rebuild DSpace, e.g. mvn -U clean package (This will recompile all DSpace backend code) 2. Redeploy DSpace, e.g. ant update (This will copy all newly built code to a project's installation directory). Depending on the user's setup they also may need to copy the updated "server" webapp over to their Tomcat webapps folder. 3. Restart Tomcat (or runnable JAR)

Workarounds

Patching the system is the recommended fix. However, if users cannot patch their system immediately, it is possible to temporarily disable all Curation Tasks by commenting out every CurationTask plugin in their curate.cfg file:

# For example, ensure every line that starts with "plugin.named.org.dspace.curate.CurationTask" is commented out

#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.NoOpCurationTask = noop
#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.ProfileFormats = profileformats
#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.RequiredMetadata = requiredmetadata
#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.ClamScan = vscan
...

Please be aware that commenting out all Curation Tasks will ensure that no curation tasks can be run from either the User Interface (in various admin tools) or from the command line. So, before commenting out these lines, ensure that users do not automatically run specific curation tasks (via dspace curate command) from scheduled cron jobs or similar.

Credits

Discovered & reported by Pablo Picurelli Ortiz (@superpegaso2703), cybersecurity student at Universidad Rey Juan Carlos. Code fix developed by Kim Shepherd (@kshepherd) of The Library Code

Severity

5.5 (Medium)


                  
                    CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 7.6.6"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.6.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 8.3"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "8.0-rc1"
            },
            {
              "fixed": "8.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 9.2"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "9.0-rc1"
            },
            {
              "fixed": "9.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10-rc1"
            },
            {
              "fixed": "10.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "10-rc1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-49831"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-08T20:25:07Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Overview\n\nThe [Curation Task](https://wiki.lyrasis.org/spaces/DSDOC9x/pages/379126845/Curation+Tasks) feature allows an output path to be used by the reporter (`-r` parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often \u0027tomcat\u0027) user is allowed.  This constitutes a Path Traversal Vulnerability in the `curate` script.\n\nThis was not a real problem when curation tasks could only be run from the command-line as a system administrator, but now that Collection/Community/Site Administrators can also run curation tasks via the web user interface, it introduces a possibility for an attacker with DSpace administrative credentials to set command parameters in such a way that output ends up in an unexpected location (for example, static resources folder in the Spring boot webapp, or overwriting a configuration file).\n\n_This vulnerability impacts DSpace versions \u003c= 7.6.6, 8.0 \u003c= 8.3, 9.0 \u003c= 9.2._ The attacker MUST already have DSpace Collection/Community/Site Administrator credentials in order to perform the attack.\n\nExpected behaviour : Only a set of configured output directories should be allowed as base paths for Curation reporter output. The fix applied here is designed to be used with other systems that need to read or write streams on disk. In addition, we do not see a need for the web-managed processes to allow the `-r` reporter output parameter at all.\n\n## Impact\n\nThe ability to overwrite a file in `/dspace/config` or `/dspace/bin` is not desired, and could result in a denial of service attack. To actually use the curation reporter to perform an attack that escalates privileges, either a custom curation task would be needed (these can only be deployed by a system administrator), or the output would have to contain some executable information that is combined with other attacks, as a way to provide a payload in a local path.\n\n## Patches\n\nThe fix is included in DSpace 7.6.7, 8.4, 9.3 and 10.0.  Please upgrade to one of these versions at the earliest convenience\n\nIf users cannot upgrade immediately, it is possible to manually patch their DSpace backend. (No changes are necessary to the frontend.) A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.x. \n* Pull request for 9.x: https://github.com/DSpace/DSpace/pull/12552  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12552.patch))\n    * This 9.x patch file also resolves a similar [path traversal vulnerability in LDN messages](https://github.com/DSpace/DSpace/security/advisories/GHSA-9qm4-rh6w-pq5x)\n* Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12540  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12540.patch))\n    * This 8.x patch file also resolves a similar [path traversal vulnerability in LDN messages](https://github.com/DSpace/DSpace/security/advisories/GHSA-9qm4-rh6w-pq5x)\n* Pull request for 7.x: https://github.com/DSpace/DSpace/pull/12539  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12539.patch))\n\n### Apply the patch to a user\u0027s DSpace\nIf at all possible, DSpace maintainers recommend disabling the ORE Crosswalk (see below) or upgrading users\u0027 DSpace site based on the upgrade instructions. However, if usersare unable to do so, they can manually apply the above patches to their DSpace backend as follows:\n1. Download the appropriate patch file to the machine where DSpace backend is running\n2. From the `[dspace-src]` folder, apply the patch, e.g. `git apply [name-of-file].patch`\n3. Now, update the DSpace site (based loosely on the Upgrade instructions). This generally involves three steps:\n    1. Rebuild DSpace, e.g. `mvn -U clean package`  (This will recompile all DSpace backend code)\n    2. Redeploy DSpace, e.g. `ant update`  (This will copy all newly built code to a project\u0027s installation directory). Depending on the user\u0027s setup they also may need to copy the updated \"server\" webapp over to their Tomcat webapps folder.\n    3. Restart Tomcat (or runnable JAR)\n\n## Workarounds\n**Patching the system is the recommended fix.** However, if users cannot patch their system immediately, it is possible to **temporarily disable all Curation Tasks** by commenting out every `CurationTask` plugin in their `curate.cfg` file:\n```\n# For example, ensure every line that starts with \"plugin.named.org.dspace.curate.CurationTask\" is commented out\n\n#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.NoOpCurationTask = noop\n#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.ProfileFormats = profileformats\n#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.RequiredMetadata = requiredmetadata\n#plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.ClamScan = vscan\n...\n```\n\nPlease be aware that commenting out all Curation Tasks will ensure that no curation tasks can be run from either the User Interface (in various admin tools) or from the command line.  So, before commenting out these lines, ensure that users do not automatically run specific curation tasks (via `dspace curate` command) from scheduled cron jobs or similar.\n\n## Credits\nDiscovered \u0026 reported by Pablo Picurelli Ortiz (@superpegaso2703), cybersecurity student at Universidad Rey Juan Carlos.\nCode fix developed by Kim Shepherd (@kshepherd) of The Library Code",
  "id": "GHSA-v66x-68f2-pxf5",
  "modified": "2026-07-08T20:25:08Z",
  "published": "2026-07-08T20:25:07Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/DSpace/DSpace/security/advisories/GHSA-v66x-68f2-pxf5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/DSpace/DSpace"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "DSpace has a possible Path Traversal Vulnerability in its Curation Task Reporter output path"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

CVE-2026-49831 (GCVE-0-2026-49831)

FKIE_CVE-2026-49831

GHSA-V66X-68F2-PXF5

Overview

Impact

Patches

Apply the patch to a user's DSpace

Workarounds

Credits

Tags

Sightings

Nomenclature