cve.bz

CVE-2026-59990 typelevel jawn

7.5 highEPSS 0.6%Fix available

High (7.5) in typelevel jawn. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.typelevel:jawn-parser_2.12 1.7.0.

On this page
Jawn is an open source JSON parser. Prior to 1.7.0, Jawn parse methods accept arbitrarily deep JSON array and object nesting without a depth limit, allowing a remote attacker who can submit untrusted JSON to grow parser contexts until the JVM heap is exhausted. The resulting java.lang.OutOfMemoryError is a fatal Scala error that is not ordinarily handled by scala.util.Try or cats.effect.IO, causing denial of service. This issue is fixed in version 1.7.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • org.typelevel:jawn-parser_2.12 (Maven): fixed in 1.7.0
  • org.typelevel:jawn-parser_2.13 (Maven): fixed in 1.7.0
  • org.typelevel:jawn-parser_3 (Maven): fixed in 1.7.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-59990 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59990?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59990?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59990 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
typelevel jawn< 1.7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cc4v-rvgp-2pf3Mavenorg.typelevel:jawn-parser_2.12<1.7.01.7.0
GHSA-cc4v-rvgp-2pf3Mavenorg.typelevel:jawn-parser_2.13<1.7.01.7.0
GHSA-cc4v-rvgp-2pf3Mavenorg.typelevel:jawn-parser_3<1.7.01.7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14jawnno fix listedDEBIAN-CVE-2026-59990
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morejawnno fix listedUBUNTU-CVE-2026-59990

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON