Skip to main content
VulnerabilityPublished Updated

CVE-2026-75140: jhy soup · Unthrottled Resource Allocation

Affects jhy soupSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
jhysoupAffected
  • <=1.23.1
Fixed in–
GitHubsouppkg:github/soupOther threatsAffected
  • <=1.23.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available as the vulnerability is resolved in commit 862ba2f. Users should upgrade jsoup to a version including this fix to prevent exploitation. No additional mitigations are specified.

Description

jsoup versions up to 1.23.1 contain a vulnerability in XmlTreeBuilder that allows remote attackers to exhaust JVM heap memory by providing a deeply nested XML document with uniquely-namespaced elements. This leads to an OutOfMemoryError and application termination. The issue is fixed in a later commit.

References

Community reviews

Loading reviews…