# CVE-2026-49831: DSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability) > An attacker can write files to arbitrary locations on the server via the Curation Task Reporter, potentially modifying system files. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Sep 2026 - **Updated:** 2 Sep 2026 - **Also known as:** GHSA-v66x-68f2-pxf5 ## What is CVE-2026-49831? CVE-2026-49831 is a medium-severity path traversal vulnerability in DSpace, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-49831? 8 open source packages ship an affected version, including org.dspace:dspace-api. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.dspace:dspace-api` | Maven | All versions | 7.6.7 | | `org.dspace:dspace-api` | Maven | All versions | 7.6.7 | | `org.dspace:dspace-api` | Maven | From 10-rc1 | 10.0 | | `org.dspace:dspace-api` | Maven | From 10-rc1 | 10.0 | | `org.dspace:dspace-api` | Maven | From 8.0-rc1 | 8.4 | | `org.dspace:dspace-api` | Maven | From 8.0-rc1 | 8.4 | | `org.dspace:dspace-api` | Maven | From 9.0-rc1 | 9.3 | | `org.dspace:dspace-api` | Maven | From 9.0-rc1 | 9.3 | ## How do I fix CVE-2026-49831? Upgrade org.dspace:dspace-api to a fixed version for your release line: 7.6.7, 10.0, 8.4 or 9.3. ## Is CVE-2026-49831 being exploited? There is no known exploitation of CVE-2026-49831 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-49831 and fix it if it is affected. What it is: CVE-2026-49831 is a medium-severity path traversal vulnerability in DSpace, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-49831 in the wild and no public exploit code. Affected packages and fixed versions: - org.dspace:dspace-api (Maven): affected all versions; fixed in 7.6.7 - org.dspace:dspace-api (Maven): affected all versions; fixed in 7.6.7 - org.dspace:dspace-api (Maven): affected from 10-rc1; fixed in 10.0 - org.dspace:dspace-api (Maven): affected from 10-rc1; fixed in 10.0 - org.dspace:dspace-api (Maven): affected from 8.0-rc1; fixed in 8.4 - org.dspace:dspace-api (Maven): affected from 8.0-rc1; fixed in 8.4 - org.dspace:dspace-api (Maven): affected from 9.0-rc1; fixed in 9.3 - org.dspace:dspace-api (Maven): affected from 9.0-rc1; fixed in 9.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-49831/ (Markdown: https://insights.sbomify.com/CVE-2026-49831/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49831 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49831 - OSV: https://osv.dev/vulnerability/CVE-2026-49831 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-49831/ Summaries are generated and may contain mistakes; the official description above is the record.