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.
CVE-2026-61814
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 23, 2026v1.7.0
Patch available: typelevel/jawn v1.7.0
https://github.com/typelevel/jawn/releases/tag/v1.7.0commit cddcd5e3387c (typelevel/jawn)
Patch available: typelevel/jawn v1.7.0 (contains commit cddcd5e3387c)
https://github.com/typelevel/jawn/commit/cddcd5e3387c356b05953f7b2af103d309687e4bQuadratic parsing effort in AsyncParser · Advisory · typelevel/jawn · GitHub
https://github.com/typelevel/jawn/security/advisories/GHSA-w4cm-gvhj-cgw6Vendor Advisories for CVE-2026-61814(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 19:11 UTCEG score recompute
- 2026-09-23 20:22 UTCEG score recompute
- 2026-09-23 19:48 UTCEG score recompute
- 2026-09-23 19:18 UTCEG score recompute
- 2026-09-23 18:49 UTCEG score recompute
- 2026-09-23 18:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-61814?
When was CVE-2026-61814 disclosed?
Is CVE-2026-61814 actively exploited?
What is the CVSS score of CVE-2026-61814?
How do I remediate CVE-2026-61814?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61814
Is Your Infrastructure Affected by CVE-2026-61814?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.