Skip to content
Applications

CVE-2026-75140

8.7
High
EPSS 0.53%Patch availableAug 22, 2026

jsoup XML parser OOM via deeply nested uniquely-namespaced elements

common questions

Is CVE-2026-75140 being exploited?

Not confirmed. CVE-2026-75140 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.

How severe is CVE-2026-75140?

CVE-2026-75140 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-75140?

Yes. A fix has been recorded for CVE-2026-75140. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-75140 affect?

CVE-2026-75140 affects jsoup <= 1.23.2, Java applications using jsoup XmlTreeBuilder, Servers parsing untrusted XML. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75140?

Upgrade jsoup to the patched commit/release (862ba2f) and validate/restrict XML nesting.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
jsoup <= 1.23.2Java applications using jsoup XmlTreeBuilderServers parsing untrusted XML
impact

Remote resource exhaustion: crafted XML triggers JVM OutOfMemoryError, causing application crash/denial of service.

action required

Patch when possible

affected versions
jhy soup
  • affected<= 1.23.1
vendor says fixed in862ba2f1d48ee95609183dbcfc848c9fd7afc76a

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free