CVE-2026-49832

HIGHPre-NVD 8.08.0
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.0 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
8.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.0Exploit: NoneExposed: 0

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

DSpace has possible Remote Code Execution (RCE) through Velocity Templates used by LDN

Overview

Remote Code Execution (RCE) is possible via Velocity Templates used by DSpace for COAR Notify/LDN messages. _This vulnerability impacts DSpace versions 8.0 <= 8.3, 9.0 <= 9.2._ The attacker MUST already have DSpace administrator credentials in order to perform the attack.

This attack is related to the path traversal attack identified in GHSA-9qm4-rh6w-pq5x as it was the impactful part of the "proof-of-concept" attack chain.

Impact

When chained with the LDN Path Traversal Attack identified in GHSA-9qm4-rh6w-pq5x, it may be possible to execute Java directly from Velocity templates using reflection. This is a very high impact vulnerability, but the attack can only be performed by a user that has DSpace Administrator privileges. Disabling LDN (see below) removes all known attack paths.

Velocity is also used for email templating, but there is no known attack path via emails templates. Nonetheless, the patches below also apply to email templates.

Patches

The fix is included in DSpace 8.4, 9.3 and 10.0. Please upgrade to one of these versions or disable LDN (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 8.x or 9.x. * Pull request for 9.x: https://github.com/DSpace/DSpace/pull/12548 (Downloadable patch file) * Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12549 (Downloadable patch file)

Apply the patch to a DSpace instance

If at all possible, DSpace project maintainers recommend disabling LDN (see below) or upgrading a DSpace site based on the upgrade instructions. However, if users are unable to do so, they can manually apply the above patches to their Space 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 application's 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 the application's installation directory). Depending on an application's setup users also may need to copy the updated "server" webapp over to their Tomcat webapps folder.
  • Restart Tomcat (or runnable JAR)

Workarounds

* In dspace.cfg or local.cfg, disable LDN (set ldn.enabled=false) if it is not crucial to the operation of the repository. (NOTE: LDN is disabled by default, so many DSpace sites may not use this feature) * Once users have patched theirr site or upgraded, they may safely enable LDN again.

Resources

This vulnerability is similar to vulnerabilities reported by Velocity itself: * Velocity 2.2. CVE: https://www.cve.org/CVERecord?id=CVE-2020-13936 * This was patched in Velocity 2.3, and DSpace already includes this patch.

Credits

Discovered & reported by Pablo Picurelli Ortiz (@superpegaso2703), cybersecurity student at Universidad Rey Juan Carlos. Reported as a possible attack combined with the LDN Path Traversal vulnerability. Code fix developed by Kim Shepherd (@kshepherd) of The Library Code

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

Published

July 8, 2026

Last Modified

July 8, 2026

Vendor Advisories for CVE-2026-49832(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 14× in last 7d / 15× 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-15 22:48 UTCEG score recompute
  2. 2026-07-15 10:39 UTCEG score recompute
  3. 2026-07-14 22:30 UTCEG score recompute
  4. 2026-07-14 10:22 UTCEG score recompute
  5. 2026-07-13 22:14 UTCEG score recompute
  6. 2026-07-13 10:06 UTCEG score recompute
  7. 2026-07-12 21:53 UTCEG score recompute
  8. 2026-07-12 09:44 UTCEG score recompute
  9. 2026-07-11 21:36 UTCEG score recompute
  10. 2026-07-11 09:28 UTCEG score recompute
  11. 2026-07-10 21:20 UTCEG score recompute
  12. 2026-07-10 09:12 UTCEG score recompute
  13. 2026-07-09 21:03 UTCEG score recompute
  14. 2026-07-09 08:55 UTCEG score recompute
  15. 2026-07-08 20:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-49832?
CVE-2026-49832 is a high vulnerability published on July 8, 2026. DSpace has possible Remote Code Execution (RCE) through Velocity Templates used by LDN Overview Remote Code Execution (RCE) is possible via Velocity Templates used by DSpace for COAR Notify/LDN messages. This vulnerability impacts DSpace versions 8.0 <= 8.3, 9.0 <= 9.2. The attacker MUST already…
When was CVE-2026-49832 disclosed?
CVE-2026-49832 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-49832?
CVE-2026-49832 has a CVSS v4.0 base score of 8.0 (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-49832?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49832, 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-49832

Explore →

Is Your Infrastructure Affected by CVE-2026-49832?

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

Start Free Scan →Browse All CVEs