NVD / CVE Program· CNA GitHub_M

CVE-2025-53622: DSpace has path traversal vulnerability in Simple Archive Format (SAF) package import via contents file

Noroxi assessment

Priority: Monitor (action score 20/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: org.dspace:dspace-api (Maven) 8.2, 9.1, 7.6.4.

Low priority for now. Upgrade to org.dspace:dspace-api (Maven) 8.2, 9.1, 7.6.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.4, 8.2, and 9.1, a path traversal vulnerability is possible during the import of an archive (in Simple Archive Format), either from command-line (`./dspace import` command) or from the "Batch Import (Zip)" user interface feature. An attacker may craft a malicious Simple Archive Format (SAF) package where the `contents` file references any system files (using relative traversal sequences) which are readable by the Tomcat user. If such a package is imported, this will result in sensitive content disclose, including retrieving arbitrary files or configurations from the server where DSpace is running. The Simple Archive Format (SAF) importer / Batch Import (Zip) is only usable by site administrators (from user interface / REST API) or system administrators (from command-line). Therefore, to exploit this vulnerability, the malicious payload would have to be provided by an attacker and trusted by an administrator (who would trigger the import). The fix is included in DSpace 7.6.4, 8.2 and 9.1. For those who cannot upgrade immediately, it is possible to manually patch the 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.0. Although it is not possible to fully protect the system via workarounds, one may can apply a best practice. Administrators must carefully inspect any SAF archives (they did not construct themselves) before importing, paying close attention to the `contents` file to validate it does not reference files outside of the SAF archives.

MediumCVSS 5.2 · v3.1—No exploit Fix available

Path traversal

GHSA-vhvx-8xgc-99wf

Published: Jul 15, 2025
Updated: Jun 17, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 20 / 40 · 5.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 5.2; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

DSpace DSpace
- < 7.6.4, >= 8.0, < 8.2, >= 9.0, < 9.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.dspace:dspace-api	from 8.0 · before 8.2	8.2
Maven	org.dspace:dspace-api	from 9.0 · before 9.1	9.1
Maven	org.dspace:dspace-api	before 7.6.4	7.6.4

Same product

dspace: all records

Other highest-scoring records for the same primary product.

CVE-2026-49832DSpace: Remote Code Execution (RCE) possible in Velocity Templates used by LDN
32Monitor
CVE-2025-53621DSpace vulnerable to XML External Entity (XXE) injection in import via Simple Archive Format (SAF) or import from external sources
27Monitor
CVE-2026-49833DSpace: Path Traversal possible in LDN message generation
22Monitor

Published before and after this one in the same product

← EarlierCVE-2024-38364Jun 25, 2024 · DSpace Cross Site Scripting (XSS) via a deposited HTML/XML document
10Monitor
Later →CVE-2026-49830Sep 2, 2026 · DSpace: ORE resource URI does not validate scheme for non-web resources
17Monitor
Later →CVE-2026-49831Sep 2, 2026 · DSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability)
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.dspace:dspace-api	7.6.4	Package registry (OSV)
Maven:org.dspace:dspace-api	8.2	Package registry (OSV)
Maven:org.dspace:dspace-api	9.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-49831414 days apartDSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability)
22Monitor
CVE-2026-49833414 days apartDSpace: Path Traversal possible in LDN message generation
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: low · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: Low

Weakness class (CWE)

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

CVSS vector

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

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/DSpace/DSpace/pull/11036

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records