CVE-2026-68494

CVEs › CVE-2026-68494

Description

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength() into a new _setIntLength() helper and invoked it wherever the integer portion of a number is decided: a terminator byte arrives, a '.' or 'e'/'E' is seen, or input ends inside a fully buffered value. It was not invoked on the attacker-relevant path where the parser runs out of input while still inside the MINOR_NUMBER_INTEGER_DIGITS minor state and returns NOT_AVAILABLE to the caller. As a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, keeps the parser inside MINOR_NUMBER_INTEGER_DIGITS indefinitely. _textBuffer.expandCurrentSegment() grows the accumulator on every chunk while validateIntegerLength() is never called. The accumulator is bounded only by maxStringLength (20 MiB by default) rather than by maxNumberLength (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java char values occupy two bytes, a single connection can be driven to approximately 40 MiB of heap before the validator finally fires when the value completes. The equivalent fraction-path code is correct: _finishFloatFraction() calls _setFractLength() before its NOT_AVAILABLE return. The missing call affects the integer-digit paths in _startPositiveNumber(), _startNegativeNumber() and _finishNumberIntegralPart() in NonBlockingUtf8JsonParserBase. Impact: reactive frameworks such as Spring WebFlux/Reactor, Quarkus, Helidon and Vert.x feed inbound HTTP or gRPC bytes to the async parser as they arrive, which is precisely the chunked-feed shape required. Operators who set StreamReadConstraints.maxNumberLength expecting it to cap memory per number value do not get that guarantee; memory accumulates per concurrent connection and attacker-controlled concurrency can exhaust the JVM heap. The synchronous parsers (UTF8StreamJsonParser, ReaderBasedJsonParser) and the async parser operating on complete input are not affected. Exploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed. This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and tools.jackson.core:jackson-core from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because StreamReadConstraints -- which defines the maxNumberLength setting -- was first introduced in jackson-core 2.15.0, so no such constraint exists to be bypassed in earlier releases. Note that GHSA-r7wm-3cxj-wff9 states the affected 2.x range without a lower bound. The 2.22.x and 3.2.x release lines are not affected: those branches were created after the fix commit landed on 2026-05-21 and therefore contain it from their initial releases (2.22.0, tagged 2026-06-03, and 3.2.0, tagged 2026-06-08).

Overview

State: PUBLISHED
Assigner (CNA): HeroDevs
CVSS severity: HIGH
CVSS score: 8.7 / 10
CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Effective score: 8.7 / 10 HIGH source: CNA overview
CWE(s): CWE-770
Reserved: 2026-07-30
Published: 2026-08-04 14:39 UTC
Last updated: 2026-08-05 01:39 UTC
Source: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/68xxx/CVE-2026-68494.json
Linked Threat: CVE-2026-68494 — jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for CVE-2026-18401 / GHSA-72hv-8253-57qq)

Affected products (2)

Vendor	Product	Versions	Platforms
FasterXML	jackson-core	`2.15.0` (affected), `2.18.8` (unaffected), `2.19.0` (affected), `2.21.4` (unaffected)	—
FasterXML	jackson-core	`3.0.0` (affected), `3.1.4` (unaffected)	—

Vendor references (7)

References embedded in the original CVE record by the assigning CNA.

GHSA-r7wm-3cxj-wff9 vendor-advisory
FasterXML/jackson-core#1611 - Apply number-length validator on streaming integer path of async parser patch
FasterXML/jackson-core@050b429 patch
FasterXML/jackson-core@4cdd529 patch
FasterXML/jackson-core@c5941e5 patch
CVE-2026-18401 - original issue for which this is an incomplete fix related
GHSA-72hv-8253-57qq - original advisory for which this is an incomplete fix related

Web references (0)

DuckDuckGo results ranked by threat-intel / vendor advisory domains. Generated by the 🔎 Find references (web) button above — same flow as the Remediations search.

No web references attached yet.

AI Forensic Analysis

Only Available for Registered Users. Sign in to view.

Raw JSON

The full cvelistV5 record. Download as CVE-2026-68494.json.

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-68494",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-04T17:53:50.672098Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-04T17:55:41.940Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://github.com/FasterXML/jackson-core/security/advisories/GHSA-r7wm-3cxj-wff9"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "com.fasterxml.jackson.core:jackson-core",
          "product": "jackson-core",
          "programFiles": [
            "src/main/java/com/fasterxml/jackson/core/json/async/NonBlockingUtf8JsonParserBase.java"
          ],
          "programRoutines": [
            {
              "name": "NonBlockingUtf8JsonParserBase._startPositiveNumber"
            },
            {
              "name": "NonBlockingUtf8JsonParserBase._startNegativeNumber"
            },
            {
              "name": "NonBlockingUtf8JsonParserBase._finishNumberIntegralPart"
            }
          ],
          "repo": "https://github.com/FasterXML/jackson-core",
          "vendor": "FasterXML",
          "versions": [
            {
              "lessThan": "2.18.8",
              "status": "affected",
              "version": "2.15.0",
              "versionType": "maven"
            },
            {
              "status": "unaffected",
              "version": "2.18.8",
              "versionType": "maven"
            },
            {
              "lessThan": "2.21.4",
              "status": "affected",
              "version": "2.19.0",
              "versionType": "maven"
            },
            {
              "status": "unaffected",
              "version": "2.21.4",
              "versionType": "maven"
            }
          ]
        },
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "tools.jackson.core:jackson-core",
          "product": "jackson-core",
          "programFiles": [
            "src/main/java/tools/jackson/core/json/async/NonBlockingUtf8JsonParserBase.java"
          ],
          "programRoutines": [
            {
              "name": "NonBlockingUtf8JsonParserBase._startPositiveNumber"
            },
            {
              "name": "NonBlockingUtf8JsonParserBase._startNegativeNumber"
            },
            {
              "name": "NonBlockingUtf8JsonParserBase._finishNumberIntegralPart"
            }
          ],
          "repo": "https://github.com/FasterXML/jackson-core",
          "vendor": "FasterXML",
          "versions": [
            {
              "lessThan": "3.1.4",
              "status": "affected",
              "version": "3.0.0",
              "versionType": "maven"
            },
            {
              "status": "unaffected",
              "version": "3.1.4",
              "versionType": "maven"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "tonghuaroot"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "tonghuaroot"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "cowtowncoder (Tatu Saloranta)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "<p>The fix released in jackson-core 2.18.6 and 2.21.1 for <b>CVE-2026-18401</b> (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass.</p><p>The earlier fix wired <tt>validateIntegerLength()</tt> into a new <tt>_setIntLength()</tt> helper and invoked it wherever the integer portion of a number is <i>decided</i>: a terminator byte arrives, a <tt>.</tt> or <tt>e</tt>/<tt>E</tt> is seen, or input ends inside a fully buffered value. It was not invoked on the attacker-relevant path where the parser runs out of input while still inside the <tt>MINOR_NUMBER_INTEGER_DIGITS</tt> minor state and returns <tt>NOT_AVAILABLE</tt> to the caller.</p><p>As a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, keeps the parser inside <tt>MINOR_NUMBER_INTEGER_DIGITS</tt> indefinitely. <tt>_textBuffer.expandCurrentSegment()</tt> grows the accumulator on every chunk while <tt>validateIntegerLength()</tt> is never called. The accumulator is bounded only by <tt>maxStringLength</tt> (20 MiB by default) rather than by <tt>maxNumberLength</tt> (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java <tt>char</tt> values occupy two bytes, a single connection can be driven to approximately 40 MiB of heap before the validator finally fires when the value completes.</p><p>The equivalent fraction-path code is correct: <tt>_finishFloatFraction()</tt> calls <tt>_setFractLength()</tt> before its <tt>NOT_AVAILABLE</tt> return. The missing call affects the integer-digit paths in <tt>_startPositiveNumber()</tt>, <tt>_startNegativeNumber()</tt> and <tt>_finishNumberIntegralPart()</tt> in <tt>NonBlockingUtf8JsonParserBase</tt>.</p><p><b>Impact:</b> reactive frameworks such as Spring WebFlux/Reactor, Quarkus, Helidon and Vert.x feed inbound HTTP or gRPC bytes to the async parser as they arrive, which is precisely the chunked-feed shape required. Operators who set <tt>StreamReadConstraints.maxNumberLength</tt> expecting it to cap memory per number value do not get that guarantee; memory accumulates per concurrent connection and attacker-controlled concurrency can exhaust the JVM heap. The synchronous parsers (<tt>UTF8StreamJsonParser</tt>, <tt>ReaderBasedJsonParser</tt>) and the async parser operating on complete input are not affected.</p><p>Exploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed.</p><p>This issue affects <tt>com.fasterxml.jackson.core:jackson-core</tt> from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and <tt>tools.jackson.core:jackson-core</tt> from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because <tt>StreamReadConstraints</tt> -- which defines the <tt>maxNumberLength</tt> setting -- was first introduced in jackson-core 2.15.0, so no such constraint exists to be bypassed in earlier releases. Note that GHSA-r7wm-3cxj-wff9 states the affected 2.x range without a lower bound.</p><p>The 2.22.x and 3.2.x release lines are not affected: those branches were created after the fix commit landed on 2026-05-21 and therefore contain it from their initial releases (2.22.0, tagged 2026-06-03, and 3.2.0, tagged 2026-06-08).</p>"
            }
          ],
          "value": "The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass.\n\nThe earlier fix wired validateIntegerLength() into a new _setIntLength() helper and invoked it wherever the integer portion of a number is decided: a terminator byte arrives, a '.' or 'e'/'E' is seen, or input ends inside a fully buffered value. It was not invoked on the attacker-relevant path where the parser runs out of input while still inside the MINOR_NUMBER_INTEGER_DIGITS minor state and returns NOT_AVAILABLE to the caller.\n\nAs a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, keeps the parser inside MINOR_NUMBER_INTEGER_DIGITS indefinitely. _textBuffer.expandCurrentSegment() grows the accumulator on every chunk while validateIntegerLength() is never called. The accumulator is bounded only by maxStringLength (20 MiB by default) rather than by maxNumberLength (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java char values occupy two bytes, a single connection can be driven to approximately 40 MiB of heap before the validator finally fires when the value completes.\n\nThe equivalent fraction-path code is correct: _finishFloatFraction() calls _setFractLength() before its NOT_AVAILABLE return. The missing call affects the integer-digit paths in _startPositiveNumber(), _startNegativeNumber() and _finishNumberIntegralPart() in NonBlockingUtf8JsonParserBase.\n\nImpact: reactive frameworks such as Spring WebFlux/Reactor, Quarkus, Helidon and Vert.x feed inbound HTTP or gRPC bytes to the async parser as they arrive, which is precisely the chunked-feed shape required. Operators who set StreamReadConstraints.maxNumberLength expecting it to cap memory per number value do not get that guarantee; memory accumulates per concurrent connection and attacker-controlled concurrency can exhaust the JVM heap. The synchronous parsers (UTF8StreamJsonParser, ReaderBasedJsonParser) and the async parser operating on complete input are not affected.\n\nExploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed.\n\nThis issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and tools.jackson.core:jackson-core from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because StreamReadConstraints -- which defines the maxNumberLength setting -- was first introduced in jackson-core 2.15.0, so no such constraint exists to be bypassed in earlier releases. Note that GHSA-r7wm-3cxj-wff9 states the affected 2.x range without a lower bound. The 2.22.x and 3.2.x release lines are not affected: those branches were created after the fix commit landed on 2026-05-21 and therefore contain it from their initial releases (2.22.0, tagged 2026-06-03, and 3.2.0, tagged 2026-06-08)."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-130",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-130 Excessive Allocation"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "Application streams attacker-supplied JSON to the non-blocking parser one network chunk at a time, for example via Jackson2JsonDecoder on the Flux<DataBuffer> streaming-decode path in Spring WebFlux, or any direct use of JsonFactory.createNonBlockingByteArrayParser() / createNonBlockingByteBufferParser()."
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-770",
              "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T01:39:56.955Z",
        "orgId": "36c7be3b-2937-45df-85ea-ca7133ea542c",
        "shortName": "HeroDevs"
      },
      "references": [
        {
          "name": "GHSA-r7wm-3cxj-wff9",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/FasterXML/jackson-core/security/advisories/GHSA-r7wm-3cxj-wff9"
        },
        {
          "name": "FasterXML/jackson-core#1611 - Apply number-length validator on streaming integer path of async parser",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/FasterXML/jackson-core/pull/1611"
        },
        {
          "name": "FasterXML/jackson-core@050b429",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/FasterXML/jackson-core/commit/050b429804dce2a7e08f0be1b0b4c3d040fdb9cd"
        },
        {
          "name": "FasterXML/jackson-core@4cdd529",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/FasterXML/jackson-core/commit/4cdd529749da396cc7edf6d4a2aad41d47902641"
        },
        {
          "name": "FasterXML/jackson-core@c5941e5",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/FasterXML/jackson-core/commit/c5941e5aae7fd5aeac55d66933cfb82b9aabeef8"
        },
        {
          "name": "CVE-2026-18401 - original issue for which this is an incomplete fix",
          "tags": [
            "related"
          ],
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-18401"
        },
        {
          "name": "GHSA-72hv-8253-57qq - original advisory for which this is an incomplete fix",
          "tags": [
            "related"
          ],
          "url": "https://github.com/advisories/GHSA-72hv-8253-57qq"
        }
      ],
      "source": {
        "advisory": "GHSA-r7wm-3cxj-wff9",
        "discovery": "EXTERNAL"
      },
      "tags": [
        "x_open-source"
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-05-20T22:33:50.000Z",
          "value": "Fix merged upstream via FasterXML/jackson-core#1611 (milestone 2.18.8)"
        },
        {
          "lang": "en",
          "time": "2026-07-10T00:00:00.000Z",
          "value": "GHSA-r7wm-3cxj-wff9 published by the maintainer in FasterXML/jackson-core"
        },
        {
          "lang": "en",
          "time": "2026-07-21T00:00:00.000Z",
          "value": "Advisory reviewed and published to the GitHub Advisory Database"
        }
      ],
      "title": "jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for CVE-2026-18401 / GHSA-72hv-8253-57qq)",
      "x_generator": {
        "engine": "Vulnogram 0.5.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "36c7be3b-2937-45df-85ea-ca7133ea542c",
    "assignerShortName": "HeroDevs",
    "cveId": "CVE-2026-68494",
    "datePublished": "2026-08-04T14:39:14.471Z",
    "dateReserved": "2026-07-30T15:20:37.472Z",
    "dateUpdated": "2026-08-05T01:39:56.955Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}