DSpace: Path Traversal possible in LDN message generation

published 2026-07-08 4 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-70235 , GHSA-9qm4-rh6w-pq5x

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits: 0; none known

DSpace open source software is a repository application which provides durable access to digital resources. From versions 8.0-rc1 to before 8.4, 9.0-rc1 to before 9.3, and 10-rc1 to before 10.0, a path traversal vulnerability is possible via the COAR Notify / LDN service in DSpace. The attacker MUST already have DSpace administrator credentials in order to perform the attack. When reading a file input stream of an "inbound pattern" / "template", used to generate an LDN message, the LDN class does not check for path traversal or restrict the templates to a known base path. This could allow an untrusted file from elsewhere in the file system (e.g. an export log, a bitstream path, a temporary file) to be read and interpreted as an Apache Velocity template. This issue has been patched in versions 8.4, 9.3, and 10.0.

Patch / fix

fixed in 3 links 2

maven org.dspace:dspace-api 8.4, 9.3, 10.0
duraspace dspace 8.4, 9.3
org.dspace dspace-api 8.4, 9.3

github.com/DSpace/DSpace#12540 pull request
github.com/DSpace/DSpace#12552 pull request

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-09-02)

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.5	CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L
GitHub	3.1	5.5	CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
maven	org.dspace:dspace-api	>=8.0-rc1, <8.4 >=9.0-rc1, <9.3 >=10.0-rc1, <10.0	8.4 9.3 10.0

Affected products

DSpace DSpace

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary