Skip to content
Fencer Vulns
high 7.5

CVE-2026-61814 json

Jawn: Quadratic parsing effort in AsyncParser

published 2026-09-23 46 d ago modified 2026-09-30 39 d ago also EUVD-2026-85551 , GHSA-w4cm-gvhj-cgw6

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

Summary

Jawn is an open source JSON parser. Prior to 1.7.0, Jawn's AsyncParser can perform quadratic work when a single JSON token is delivered across many small chunks because each absorb call rescans the incomplete token from the start. A remote attacker who controls untrusted JSON input and its chunk sizes can exhaust CPU resources and cause denial of service in applications using AsyncParser. 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
  • 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
  • jawn SLE Module for Package Hub 15 SP7 0.14.1-150200.3.6.1

suse advisories SUSE-SU-2026:4407-1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
46 d ago

Exploit prediction

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

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
  • org.typelevel jawn-parser_2.12
  • org.typelevel jawn-parser_2.13
  • org.typelevel jawn-parser_3

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-407 Inefficient Algorithmic Complexity

References

Sources

Fencer Vulns 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.