Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-68494

Vulnerability in tools.jackson.core:jackson-core (CVE-2026-68494)

Summary

Vulnerability in tools.jackson.core:jackson-core (CVE-2026-68494). Risk of unauthorized operations or information disclosure. Exploitable via b0c428e6. Mitigation: upgrade to 3.1.4 or later.

Original description

The description as published by the source.

Summary

The fix released in jackson-core 2.18.6 and 2.21.1 for GHSA-72hv-8253-57qq (Number Length Constraint Bypass in Async Parser, published 2026-02-28) is incomplete. The fix commit b0c428e6 (#1555) wired validateIntegerLength into a new _setIntLength helper and called it at every place where the integer portion of a number is decided (terminator byte arrived, . / e/E seen, end-of-feed inside a fully-buffered value). It did not call it on the much more attacker-relevant path: "ran out of input while still inside MINOR_NUMBER_INTEGER_DIGITS, return NOT_AVAILABLE to caller".

As a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, can keep the parser inside MINOR_NUMBER_INTEGER_DIGITS indefinitely. _textBuffer.expandCurrentSegment() grows on every chunk, and validateIntegerLength is never invoked. The accumulator is only gated by maxStringLength (20 MiB default) — a ~20,000x amplification of the documented maxNumberLength (1000 default).

This is the same vulnerability class, same advisory wording ("Memory Exhaustion: Unbounded allocation in TextBuffer from excessively long numbers"), same parser class — just the streaming path the original fix didn't cover. The fix to the fraction path is correct (see _finishFloatFraction at line 1834-1837 of `NonBlockingUtf8JsonParserBase.java…

Source: GitHub Security Advisories (Global) 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-68494 has been found in tools.jackson.core:jackson-core.
Attackers can target a specific entry point like b0c428e6 over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tools.jackson.core:jackson-core to 3.1.4 or later.
If unsure, ask your IT team or search "tools.jackson.core:jackson-core CVE-2026-68494" on the vendor's site.

CVE-2026-68494 (tools.jackson.core:jackson-core) — CWE-770
Attack surface: b0c428e6 / validateIntegerLength / _setIntLength / MINOR_NUMBER_INTEGER_DIGITS
Patched: 3.1.4 — 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-770) exists in tools.jackson.core:jackson-core. Attackers reach the vulnerable code path via b0c428e6.

📍 Affected scope

Check the vendor advisory for the affected versions of tools.jackson.core:jackson-core. Attack surface: b0c428e6 / validateIntegerLength / _setIntLength / MINOR_NUMBER_INTEGER_DIGITS.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.1.4.

🛡️ 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・依存マニフェストで tools.jackson.core:jackson-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade tools.jackson.core:jackson-core to 3.1.4

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

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

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

Affected packages

maven tools.jackson.core:jackson-core
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.1.4"}]}]
maven com.fasterxml.jackson.core:jackson-core
[{"type":"ECOSYSTEM","events":[{"introduced":"2.19.0"},{"fixed":"2.21.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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