CVE-2026-49830

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 4.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DSpace: ORE resource URI does not validate scheme for non-web resources

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

CVSS v3
4.4
EG Score
4.4(low)
EPSS
—
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Vendor Advisories for CVE-2026-49830(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 8× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 02:04 UTCEG score recompute
  2. 2026-07-15 04:26 UTCEG score recompute
  3. 2026-07-14 06:45 UTCEG score recompute
  4. 2026-07-13 09:04 UTCEG score recompute
  5. 2026-07-12 11:26 UTCEG score recompute
  6. 2026-07-11 13:47 UTCEG score recompute
  7. 2026-07-10 16:08 UTCEG score recompute
  8. 2026-07-09 18:26 UTCEG score recompute
  9. 2026-07-08 20:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-49830?
CVE-2026-49830 is a medium vulnerability published on July 8, 2026. DSpace: ORE resource URI does not validate scheme for non-web resources 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…
When was CVE-2026-49830 disclosed?
CVE-2026-49830 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-49830?
CVE-2026-49830 has a CVSS v4.0 base score of 4.4 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-49830?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49830, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49830

Explore →

Is Your Infrastructure Affected by CVE-2026-49830?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs