Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61814 high CVSS 7.5

Vulnerability in org.typelevel:jawn-parser_2.12 (CVE-2026-61814)

Summary

Vulnerability in org.typelevel:jawn-parser_2.12 (CVE-2026-61814). Risk of unauthorized operations or information disclosure. Exploitable via AsyncParser. Mitigation: upgrade to 1.7.0 or later.

Original description

The description as published by the source.

AsyncParser can be forced to perform O(n^2) work on the length of the input. When a single JSON token arrives across many small chunks, each absorb call rescans the incomplete token from the start.

Impact

Denial of service via CPU exhaustion when parsing untrusted JSON.

Preconditions:

  • Application uses AsyncParser
  • Attacker can send large tokens with control over chunk sizes.

Patches

Fixed in jawn-parser-1.7.0.

Workarounds

If you can't upgrade immediately:

  • Use the synchronous Parser.
  • Buffer incoming bytes into larger chunks before calling absorb

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61814 has been found in org.typelevel:jawn-parser_2.12.
Attackers can target a specific entry point like AsyncParser over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.typelevel:jawn-parser_2.12 to 1.7.0 or later.
If unsure, ask your IT team or search "org.typelevel:jawn-parser_2.12 CVE-2026-61814" on the vendor's site.

CVE-2026-61814 (org.typelevel:jawn-parser_2.12) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: AsyncParser / absorb / Parser
Patched: 1.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in org.typelevel:jawn-parser_2.12. Attackers reach the vulnerable code path via AsyncParser without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.typelevel:jawn-parser_2.12. Attack surface: AsyncParser / absorb / Parser.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.typelevel:jawn-parser_2.12 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.typelevel:jawn-parser_2.12 to 1.7.0

    ステージング環境で 1.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.typelevel:jawn-parser_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.0"}]}]
maven org.typelevel:jawn-parser_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.0"}]}]
maven org.typelevel:jawn-parser_3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details