jsoup through 1.23.2, fixed in commit 862ba2f, contains an uncontrolled resource consumption vulnerability in XmlTreeBuilder that allows remote attackers to exhaust JVM heap memory by supplying a deeply nested XML document with uniquely-namespaced elements. The builder copies the entire inherited namespace map on every start element, causing quadratic time and memory complexity, which attackers can exploit to trigger an OutOfMemoryError and terminate the application.
CVE-2026-75140
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
Advisory Details (3)
Auto-updated Aug 20, 2026jsoup Uncontrolled Resource Consumption in XmlTreeBuilder | Advisories | VulnCheck
https://www.vulncheck.com/advisories/jsoup-uncontrolled-resource-consumption-in-xmltreebuildercommit 862ba2f1d48e (jhy/jsoup)
Fix landed in jhy/jsoup commit 862ba2f1d48e — awaiting tagged release
https://github.com/jhy/jsoup/commit/862ba2f1d48ee95609183dbcfc848c9fd7afc76aOptimize XML namespace scope tracking
Fix merged in jhy/jsoup PR #2556 on 2026-08-09 — awaiting tagged release
https://github.com/jhy/jsoup/pull/2556Vendor Advisories for CVE-2026-75140(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-08-21 06:26 UTCEG score recompute
- 2026-08-21 06:26 UTCGHSA enrichment
- 2026-08-20 17:34 UTCEG score recompute
- 2026-08-20 17:17 UTCEG score recompute
- 2026-08-20 16:31 UTCEG score recompute
- 2026-08-20 16:07 UTCEG score recompute
- 2026-08-20 16:06 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-75140?
When was CVE-2026-75140 disclosed?
What is the CVSS score of CVE-2026-75140?
How do I remediate CVE-2026-75140?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75140
Is Your Infrastructure Affected by CVE-2026-75140?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.