What is the CVSS score of CVE-2026-49830?

CVE-2026-49830 has a CVSS 3.1 base score of 4.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N.

Is there a patch available for CVE-2026-49830?

Yes, a patch is available for CVE-2026-49830. Update the affected software to the latest version immediately.

DSpace CVE-2026-49830

Q: Which versions of DSpace are affected by CVE-2026-49830?

Local file inclusion in DSpace's OAI-ORE Ingestion Crosswalk allows a collection administrator to expose arbitrary server-side files as ingested bitstreams by supplying or triggering a malicious ORE…. A patch is available.

MEDIUM

Improper Input Validation (CWE-20)

2026-07-08 https://github.com/DSpace/DSpace

GHSA-c827-pw3m-67w7

Privilege Escalation Tomcat

4.4

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

4.4 MEDIUM

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

vuln.today AI

4.4 MEDIUM

Collection admin credentials required (PR:H) and attacker must control or compromise an OAI endpoint (AC:H); impact is read-only local file disclosure (C:H, I:N, A:N).

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

4.0 AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 08, 2026 - 21:56 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

10 maven packages depend on org.dspace:dspace-api (7 direct, 3 indirect)

Ecosystem-wide dependent count for version 8.0-rc1.

DescriptionGitHub Advisory

Overview

When ingesting an aggregated ORE resource by URI (using the OAI-ORE Harvester)), the ORE Ingestion Crosswalk does not validate the URI scheme. This may allow for local file inclusion via malicious paths like file:///etc/passwd. _This vulnerability impacts DSpace versions <= 7.6.6, 8.0 <= 8.3, 9.0 <= 9.2._ The attacker MUST already have DSpace collection administrator privileges in order to perform the attack.

Expected behaviour : Only external web resources should be ingested as ORE resources, preferably from the trusted endpoint.

Impact

A remote OAI endpoint configured as a harvest source for a DSpace collection can supply malicious ORE XML that results in a local file from the DSpace server being ingested as a bitstream.

Only Collection, Community and Site Administrators can configure a collection for OAI harvest, however an attacker may use stolen credentials to escalate into local file/data disclosure, or a compromised OAI endpoint could also supply malicious XML.

Patches

The fix is included in DSpace 7.6.7, 8.4, 9.3 and 10.0. Please upgrade to one of these versions or disable the ORE Crosswalk (see below).

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/12541 (Downloadable patch file)
Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12543 (Downloadable patch file)
Pull request for 7.x: https://github.com/DSpace/DSpace/pull/12542 (Downloadable patch file)

Apply the patch to a user's DSpace

If at all possible, we recommend disabling the ORE Crosswalk (see below) or upgrading a user's DSpace site based on the upgrade instructions. However, if they are unable to do so, they can manually apply the above patches to their DSpace backend as follows:

Download the appropriate patch file to the machine where DSpace backend is running
From the [dspace-src] folder, apply the patch, e.g. git apply [name-of-file].patch
Now, update the DSpace site (based loosely on the Upgrade instructions). This generally involves three steps:
Rebuild DSpace, e.g. mvn -U clean package (This will recompile all DSpace backend code)
Redeploy DSpace, e.g. ant update (This will copy all newly built code to their installation directory). Depending on their setup they also may need to copy the updated "server" webapp over to their Tomcat webapps folder.
Restart Tomcat (or runnable JAR)

Workarounds

Disable the ORE ingestion crosswalk in dspace.cfg by commenting out or removing it from the list of plugin.named.org.dspace.content.crosswalk.IngestionCrosswalk plugins:

# Remove or comment out this line
  org.dspace.content.crosswalk.OREIngestionCrosswalk = ore, \

Once they have patched their site or upgraded, they may safely enable the OREIngestionCrosswalk again.

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

AnalysisAI

Local file inclusion in DSpace's OAI-ORE Ingestion Crosswalk allows a collection administrator to expose arbitrary server-side files as ingested bitstreams by supplying or triggering a malicious ORE XML document referencing file:/// URIs. Versions 7.x through 7.6.6, 8.0-8.3, and 9.0-9.2 are confirmed affected; fixed releases (7.6.7, 8.4, 9.3, 10.0) are available per the GitHub security advisory. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

Obtain or steal DSpace collection admin credentials

Delivery

Configure collection harvest source to attacker-controlled OAI endpoint

Exploit

OAI endpoint serves ORE XML with file:/// resource URI

Execution

Unpatched crosswalk fetches local file path

Persist

Server file ingested as collection bitstream

Impact

Attacker retrieves disclosed file via DSpace interface

Access

Obtain or steal DSpace collection admin credentials

Delivery

Configure collection harvest source to attacker-controlled OAI endpoint

Exploit

OAI endpoint serves ORE XML with file:/// resource URI

Execution

Unpatched crosswalk fetches local file path

Persist

Server file ingested as collection bitstream

Impact

Attacker retrieves disclosed file via DSpace interface

Vulnerability AssessmentAI

Exploitation	Exploitation requires the attacker to hold DSpace collection administrator privileges or possess stolen credentials for an account with that role - regular authenticated users and unauthenticated users cannot exploit this. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	The CVSS 3.1 vector AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N accurately characterizes a vulnerability whose high confidentiality ceiling is substantially constrained by realistic prerequisites. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	An attacker who has obtained DSpace collection administrator credentials (via phishing, credential stuffing, or insider threat) configures a target collection to harvest from an attacker-controlled OAI endpoint. That endpoint serves ORE XML containing a resource URI of file:///etc/passwd or a DSpace configuration file path; the unpatched crosswalk fetches the local file and ingests it as a bitstream accessible through the DSpace interface. …
Remediation	Vendor-released patches are available: upgrade to DSpace 7.6.7, 8.4, 9.3, or 10.0 following standard DSpace upgrade procedures (rebuild with mvn -U clean package, redeploy with ant update, restart Tomcat). … Detailed patch versions, workarounds, and compensating controls in full report.