How severe is CVE-2026-75140?

No CVSS score has been assigned to CVE-2026-75140 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-75140?

CVE-2026-75140 affects the following packages: org.jsoup:jsoup (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-75140?

Update org.jsoup:jsoup to 1.23.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-75140 is resolved across your whole dependency graph.

How do I detect CVE-2026-75140 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jsoup:jsoup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-75140 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-75140 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-75140 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-75140?

CVE-2026-75140 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-75140?

CVE-2026-75140 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-75140 published, and has it been updated?

CVE-2026-75140 was published on August 20, 2026 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-75140 — jsoup

Fix: jhy/jsoup@862ba2f

CVE-2026-75140 is a CWE-770 vulnerability in org.jsoup:jsoup. A fix is available for org.jsoup:jsoup — see the affected versions and patch details below.

jsoup Uncontrolled Resource Consumption in XmlTreeBuilder

Also known asGHSA-65r4-943x-97jj

Published

Aug 20, 2026

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-75140.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.jsoup:jsoup

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jsoup:jsoup`	all versions	1.23.2`org.jsoup:jsoup:1.23.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jsoup:jsoup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jsoup:jsoup to 1.23.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-75140 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in jsoup. Parsing deeply nested XML documents can cause a denial of service via excessive stack consumption, leading to a StackOverflowError. An attacker who can supply untrusted XML input to an application using jsoup for parsing can exploit this to crash the application or exhaust system resources.

Workaround published by Red Hat

Validate and limit the nesting depth of XML documents before passing them to jsoup for parsing. Applications should implement input size limits and consider using iterative XML parsers for untrusted input. Where possible, restrict the sources of XML input to trusted origins only.

Source: Red Hat security advisory for CVE-2026-75140 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Quarkus 3.27.5.SP2	`jsoup`	RHSA-2026:69470
Red Hat build of Quarkus 3.33.3.SP2	`jsoup`	RHSA-2026:69440
OpenShift Developer Tools and Services 4.12	`ocp-tools-4/jenkins-rhel8:1792044326`	RHSA-2026:88152
OpenShift Developer Tools and Services 4.13	`ocp-tools-4/jenkins-rhel8:1792044327`	RHSA-2026:88149
OpenShift Developer Tools and Services 4.14	`ocp-tools-4/jenkins-rhel8:1792044382`	RHSA-2026:88151
OpenShift Developer Tools and Services 4.15	`ocp-tools-4/jenkins-rhel8:1792044386`	RHSA-2026:88150
OpenShift Developer Tools and Services 4.16	`ocp-tools-4/jenkins-rhel9:1792040287`	RHSA-2026:88156
OpenShift Developer Tools and Services 4.17	`ocp-tools-4/jenkins-rhel9:1792040131`	RHSA-2026:88159

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-75140 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works