Skip to content
Fencer Intel
high 7.5

CVE-2026-59990 json

Jawn: Uncontrolled nesting depth in JSON parser

published last mo. modified last mo. also EUVD-2026-85554 , GHSA-cc4v-rvgp-2pf3

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.typelevel:jawn-parser_2.12 1.7.0
  • maven org.typelevel:jawn-parser_2.13 1.7.0
  • maven org.typelevel:jawn-parser_3 1.7.0
  • typelevel jawn 1.7.0
  • org.typelevel jawn-parser_2.12 1.7.0
  • org.typelevel jawn-parser_2.13 1.7.0
  • org.typelevel jawn-parser_3 1.7.0

Is CVE-2026-59990 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.typelevel:jawn-parser_2.12
<1.7.0
1.7.0
maven org.typelevel:jawn-parser_2.13
<1.7.0
1.7.0
maven org.typelevel:jawn-parser_3
<1.7.0
1.7.0

Affected products

  • typelevel jawn

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.