Answer in brief
CVE-2026-61814 records a High severity (CVSS 7.5) vulnerability in Jawn: Quadratic parsing effort in AsyncParser. The current sources do not mark it as known exploited. The current feed maps typelevel/jawn (generic), org.typelevel/jawn-parser_2.12 (generic), org.typelevel/jawn-parser_2.13 (generic), org.typelevel/jawn-parser_3 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps typelevel/jawn (generic), org.typelevel/jawn-parser_2.12 (generic), org.typelevel/jawn-parser_2.13 (generic), org.typelevel/jawn-parser_3 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| typelevel/jawngeneric | <1.7.0 | 1.7.0 |
| org.typelevel/jawn-parser_2.12generic | <1.7.0 | 1.7.0 |
| org.typelevel/jawn-parser_2.13generic | <1.7.0 | 1.7.0 |
| org.typelevel/jawn-parser_3generic | <1.7.0 | 1.7.0 |
| org.typelevel:jawn-parser_2.12maven | >=0 <1.7.0 | 1.7.0 |
| org.typelevel:jawn-parser_2.12maven | <=1.6.0 | 1.7.0 |
| org.typelevel:jawn-parser_2.13maven | <=1.6.0 | 1.7.0 |
| org.typelevel:jawn-parser_2.13maven | >=0 <1.7.0 | 1.7.0 |
| org.typelevel:jawn-parser_3maven | <=1.6.0 | 1.7.0 |
| org.typelevel:jawn-parser_3maven | >=0 <1.7.0 | 1.7.0 |
Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.