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

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

Summary

Vulnerability in tools.jackson.core:jackson-databind (CVE-2026-68497). Risk of unauthorized operations or information disclosure. Exploitable via javax.xml.datatype.Duration. Mitigation: upgrade to 3.1.6 or later.

Original description

The description as published by the source.

Summary

jackson-databind 3.2.1 deserializes a JSON string bound to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) / newXMLGregorianCalendar(value). Per the XML-Schema lexical grammar these factory methods accept numeric components of arbitrary length, which the JDK materializes into java.math.BigInteger / BigDecimal using the native BigInteger(String) constructor (an O(n²) parser). Because the digits reside inside a JSON string token, jackson-core's StreamReadConstraints.maxNumberLength guard (which bounds only JSON number tokens) never fires, so there is no length limit anywhere on this path. An unauthenticated attacker can submit a single small request (e.g. ~1–5 MB) that forces tens of seconds to minutes of single-thread CPU consumption, yielding a denial of service under the default JsonMapper.builder().build() mapper with no polymorphic typing or special configuration.

Details

StreamReadConstraints.maxNumberLength (jackson-core, default 1000) bounds the text length of JSON number tokens only; it does not apply to digits inside a JSON string token (maxStringLength default is 100,000,000). jackson's own value binders compensate for this gap elsewhere — NumberDeserializers explicitly call streamReadConstraints().validateIntegerLength(text.length()) / validateFPLength(text.length()) before parsing a stringified number…

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-68497 has been found in tools.jackson.core:jackson-databind.
Attackers can target a specific entry point like javax.xml.datatype.Duration over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade tools.jackson.core:jackson-databind to 3.1.6 or later.
If unsure, ask your IT team or search "tools.jackson.core:jackson-databind CVE-2026-68497" on the vendor's site.

CVE-2026-68497 (tools.jackson.core:jackson-databind) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: javax.xml.datatype.Duration / javax.xml.datatype.XMLGregorianCalendar / java.math.BigInteger / BigDecimal
Patched: 3.1.6 — 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 tools.jackson.core:jackson-databind. Attackers reach the vulnerable code path via javax.xml.datatype.Duration without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of tools.jackson.core:jackson-databind. Attack surface: javax.xml.datatype.Duration / javax.xml.datatype.XMLGregorianCalendar / java.math.BigInteger / BigDecimal.

🔥 Severity

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

🔧 How to fix

Update to 3.1.6.

🛡️ 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-databind を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade tools.jackson.core:jackson-databind to 3.1.6

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

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

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

Affected packages

maven tools.jackson.core:jackson-databind
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.6"}]}]
maven com.fasterxml.jackson.core:jackson-databind
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.22.2"}]}]

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