# DSpace: Path Traversal is possible through LDN message generation

Advisory record · `GHSA-9qm4-rh6w-pq5x`

- **Identifiers:** `GHSA-9qm4-rh6w-pq5x` · `CVE-2026-49833`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Jul 2026, 20:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.dspace:dspace-api` (Maven): affected `>=8.0-rc1, <8.4 || >=9.0-rc1, <9.3 || >=10.0-rc1, <10.0`; fixed in `8.4`, `9.3`, `10.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected versions of org.dspace:dspace-api are 8.0 through 8.3, 9.0 through 9.2, and 10.0-rc1 range as listed in the package data. A path traversal flaw in the LDN (COAR Notify) template handling lets an attacker with DSpace administrator credentials make the server read an arbitrary file and interpret it as a Velocity template, which could disclose information or lead to arbitrary code execution. Upgrade to 8.4, 9.3, or 10.0; if that is not possible, set ldn.enabled=false in dspace.cfg or local.cfg, since LDN is disabled by default.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9qm4-rh6w-pq5x)

## Sources

- [GitHub Advisory Database: GHSA-9qm4-rh6w-pq5x](https://github.com/advisories/GHSA-9qm4-rh6w-pq5x)
- [OSV: GHSA-9qm4-rh6w-pq5x](https://osv.dev/vulnerability/GHSA-9qm4-rh6w-pq5x)
- <https://github.com/DSpace/DSpace/security/advisories/GHSA-9qm4-rh6w-pq5x>
- <https://github.com/DSpace/DSpace/pull/12540>
- <https://github.com/DSpace/DSpace>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9qm4-rh6w-pq5x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9qm4-rh6w-pq5x/>. Everything for agents: <https://agentprime.io/llms.txt>.