CVE-2026-68494 (GCVE-0-2026-68494)

Vulnerability from cvelistv5 – Published: 2026-08-04 14:39 – Updated: 2026-08-05 01:39 X_Open Source
VLAI
Title
jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for CVE-2026-18401 / GHSA-72hv-8253-57qq)
Summary
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).
Severity
8.7 (High)
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
SSVC
Exploitation: poc Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-08-04 17:53 UTC
CWE
  • CWE-770 - Allocation of Resources Without Limits or Throttling
Assigner
HeroDevs CNA under the mitre root
CNA scorecard B 82/100 over 17 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
FasterXML jackson-core Affected: 2.15.0 , < 2.18.8 (maven)
Unaffected: 2.18.8 (maven)
Affected: 2.19.0 , < 2.21.4 (maven)
Unaffected: 2.21.4 (maven)
guessed Create a notification for this product.
FasterXML jackson-core Affected: 3.0.0 , < 3.1.4 (maven)
Unaffected: 3.1.4 (maven)
guessed Create a notification for this product.
Credits
tonghuaroot tonghuaroot cowtowncoder (Tatu Saloranta)
Show details on NVD website
To clipboard 

{
  "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": "\u003cp\u003eThe fix released in jackson-core 2.18.6 and 2.21.1 for \u003cb\u003eCVE-2026-18401\u003c/b\u003e (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass.\u003c/p\u003e\u003cp\u003eThe earlier fix wired \u003ctt\u003evalidateIntegerLength()\u003c/tt\u003e into a new \u003ctt\u003e_setIntLength()\u003c/tt\u003e helper and invoked it wherever the integer portion of a number is \u003ci\u003edecided\u003c/i\u003e: a terminator byte arrives, a \u003ctt\u003e.\u003c/tt\u003e or \u003ctt\u003ee\u003c/tt\u003e/\u003ctt\u003eE\u003c/tt\u003e 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 \u003ctt\u003eMINOR_NUMBER_INTEGER_DIGITS\u003c/tt\u003e minor state and returns \u003ctt\u003eNOT_AVAILABLE\u003c/tt\u003e to the caller.\u003c/p\u003e\u003cp\u003eAs 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 \u003ctt\u003eMINOR_NUMBER_INTEGER_DIGITS\u003c/tt\u003e indefinitely. \u003ctt\u003e_textBuffer.expandCurrentSegment()\u003c/tt\u003e grows the accumulator on every chunk while \u003ctt\u003evalidateIntegerLength()\u003c/tt\u003e is never called. The accumulator is bounded only by \u003ctt\u003emaxStringLength\u003c/tt\u003e (20 MiB by default) rather than by \u003ctt\u003emaxNumberLength\u003c/tt\u003e (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java \u003ctt\u003echar\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eThe equivalent fraction-path code is correct: \u003ctt\u003e_finishFloatFraction()\u003c/tt\u003e calls \u003ctt\u003e_setFractLength()\u003c/tt\u003e before its \u003ctt\u003eNOT_AVAILABLE\u003c/tt\u003e return. The missing call affects the integer-digit paths in \u003ctt\u003e_startPositiveNumber()\u003c/tt\u003e, \u003ctt\u003e_startNegativeNumber()\u003c/tt\u003e and \u003ctt\u003e_finishNumberIntegralPart()\u003c/tt\u003e in \u003ctt\u003eNonBlockingUtf8JsonParserBase\u003c/tt\u003e.\u003c/p\u003e\u003cp\u003e\u003cb\u003eImpact:\u003c/b\u003e 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 \u003ctt\u003eStreamReadConstraints.maxNumberLength\u003c/tt\u003e 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 (\u003ctt\u003eUTF8StreamJsonParser\u003c/tt\u003e, \u003ctt\u003eReaderBasedJsonParser\u003c/tt\u003e) and the async parser operating on complete input are not affected.\u003c/p\u003e\u003cp\u003eExploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed.\u003c/p\u003e\u003cp\u003eThis issue affects \u003ctt\u003ecom.fasterxml.jackson.core:jackson-core\u003c/tt\u003e from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and \u003ctt\u003etools.jackson.core:jackson-core\u003c/tt\u003e from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because \u003ctt\u003eStreamReadConstraints\u003c/tt\u003e -- which defines the \u003ctt\u003emaxNumberLength\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eThe 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).\u003c/p\u003e"
            }
          ],
          "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 \u0027.\u0027 or \u0027e\u0027/\u0027E\u0027 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\u003cDataBuffer\u003e 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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-68494",
      "date": "2026-10-29",
      "epss": "0.00463",
      "percentile": "0.40113"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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"
                  }
                ]
              }
            ],
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "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 \u0027.\u0027 or \u0027e\u0027/\u0027E\u0027 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)."
          },
          {
            "lang": "es",
            "value": "La correcci\u00f3n lanzada en jackson-core 2.18.6 y 2.21.1 para CVE-2026-18401 (GHSA-72hv-8253-57qq, omisi\u00f3n de la restricci\u00f3n de longitud de n\u00famero en el analizador no bloqueante) est\u00e1 incompleta. Este registro cubre la omisi\u00f3n restante.\n\nLa correcci\u00f3n anterior conect\u00f3 validateIntegerLength() a una nueva funci\u00f3n auxiliar _setIntLength() y la invoc\u00f3 dondequiera que se decide la porci\u00f3n entera de un n\u00famero: llega un byte terminador, se ve un \u2019.\u2019 o una \u2019e\u2019/\u2019E\u2019, o la entrada termina dentro de un valor completamente almacenado en b\u00fafer. No se invoc\u00f3 en la ruta relevante para el atacante donde el analizador se queda sin entrada mientras a\u00fan est\u00e1 dentro del estado menor MINOR_NUMBER_INTEGER_DIGITS y devuelve NOT_AVAILABLE al llamador.\n\nComo resultado, un atacante que transmite JSON a un analizador no bloqueante en muchos fragmentos peque\u00f1os, sin enviar nunca un byte terminador, mantiene el analizador dentro de MINOR_NUMBER_INTEGER_DIGITS indefinidamente. _textBuffer.expandCurrentSegment() hace crecer el acumulador en cada fragmento mientras que validateIntegerLength() nunca se llama. El acumulador est\u00e1 limitado solo por maxStringLength (20 MiB por defecto) en lugar de por maxNumberLength (1000 por defecto), una amplificaci\u00f3n de aproximadamente 20.000x sobre el l\u00edmite documentado. Debido a que los valores char de Java ocupan dos bytes, una sola conexi\u00f3n puede ser llevada a aproximadamente 40 MiB de heap antes de que el validador finalmente se active cuando el valor se completa.\n\nEl c\u00f3digo equivalente de la ruta de fracci\u00f3n es correcto: _finishFloatFraction() llama a _setFractLength() antes de su retorno NOT_AVAILABLE. La llamada faltante afecta las rutas de d\u00edgitos enteros en _startPositiveNumber(), _startNegativeNumber() y _finishNumberIntegralPart() en NonBlockingUtf8JsonParserBase.\n\nImpacto: los frameworks reactivos como Spring WebFlux/Reactor, Quarkus, Helidon y Vert.x alimentan bytes HTTP o gRPC entrantes al analizador as\u00edncrono a medida que llegan, que es precisamente la forma de alimentaci\u00f3n en fragmentos requerida. Los operadores que configuran StreamReadConstraints.maxNumberLength esperando que limite la memoria por valor num\u00e9rico no obtienen esa garant\u00eda; la memoria se acumula por conexi\u00f3n concurrente y la concurrencia controlada por el atacante puede agotar el heap de la JVM. Los analizadores s\u00edncronos (UTF8StreamJsonParser, ReaderBasedJsonParser) y el analizador as\u00edncrono que opera con entrada completa no se ven afectados.\n\nLa explotaci\u00f3n requiere solo la capacidad de transmitir datos a un punto final de an\u00e1lisis; no se necesitan privilegios ni interacci\u00f3n del usuario.\n\nEste problema afecta a com.fasterxml.jackson.core:jackson-core desde la versi\u00f3n 2.15.0 hasta la 2.18.7, y desde la 2.19.0 hasta la 2.21.3, y a tools.jackson.core:jackson-core desde la 3.0.0 hasta la 3.1.3. Las versiones anteriores a la 2.15.0 no se ven afectadas, porque StreamReadConstraints -- que define la configuraci\u00f3n maxNumberLength -- se introdujo por primera vez en jackson-core 2.15.0, por lo que no existe tal restricci\u00f3n para ser omitida en versiones anteriores. Tenga en cuenta que GHSA-r7wm-3cxj-wff9 establece el rango 2.x afectado sin un l\u00edmite inferior. Las l\u00edneas de lanzamiento 2.22.x y 3.2.x no se ven afectadas: esas ramas se crearon despu\u00e9s de que la confirmaci\u00f3n de la correcci\u00f3n se aplicara el 21-05-2026 y por lo tanto la contienen desde sus lanzamientos iniciales (2.22.0, etiquetado el 03-06-2026, y 3.2.0, etiquetado el 08-06-2026)."
          }
        ],
        "id": "CVE-2026-68494",
        "lastModified": "2026-10-23T23:10:00.157",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 8.7,
                "baseSeverity": "HIGH",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "NONE",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "HIGH",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-68494",
                "options": [
                  {
                    "exploitation": "poc"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-04T17:53:50.672098Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-08-04T15:16:41.443",
        "references": [
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/FasterXML/jackson-core/commit/050b429804dce2a7e08f0be1b0b4c3d040fdb9cd"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/FasterXML/jackson-core/commit/4cdd529749da396cc7edf6d4a2aad41d47902641"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/FasterXML/jackson-core/commit/c5941e5aae7fd5aeac55d66933cfb82b9aabeef8"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/FasterXML/jackson-core/pull/1611"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/FasterXML/jackson-core/security/advisories/GHSA-r7wm-3cxj-wff9"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://github.com/advisories/GHSA-72hv-8253-57qq"
          },
          {
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "url": "https://www.cve.org/CVERecord?id=CVE-2026-18401"
          },
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "url": "https://github.com/FasterXML/jackson-core/security/advisories/GHSA-r7wm-3cxj-wff9"
          }
        ],
        "sourceIdentifier": "36c7be3b-2937-45df-85ea-ca7133ea542c",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-770"
              }
            ],
            "source": "36c7be3b-2937-45df-85ea-ca7133ea542c",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-10-30T00:09:21+00:00",
      "cve": "CVE-2026-68494",
      "id": "CVE-2026-68494",
      "initial_release_date": "2026-08-04T14:39:14.471000+00:00",
      "product_status:fixed": "942",
      "product_status:known_affected": "191",
      "product_status:known_not_affected": "4183",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via incomplete fix in async JSON parser",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68494.json",
      "version": "3"
    },
    "vulnrichment": {
      "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:54:23.935Z",
              "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": "\u003cp\u003eThe fix released in jackson-core 2.18.6 and 2.21.1 for \u003cb\u003eCVE-2026-18401\u003c/b\u003e (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass.\u003c/p\u003e\u003cp\u003eThe earlier fix wired \u003ctt\u003evalidateIntegerLength()\u003c/tt\u003e into a new \u003ctt\u003e_setIntLength()\u003c/tt\u003e helper and invoked it wherever the integer portion of a number is \u003ci\u003edecided\u003c/i\u003e: a terminator byte arrives, a \u003ctt\u003e.\u003c/tt\u003e or \u003ctt\u003ee\u003c/tt\u003e/\u003ctt\u003eE\u003c/tt\u003e 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 \u003ctt\u003eMINOR_NUMBER_INTEGER_DIGITS\u003c/tt\u003e minor state and returns \u003ctt\u003eNOT_AVAILABLE\u003c/tt\u003e to the caller.\u003c/p\u003e\u003cp\u003eAs 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 \u003ctt\u003eMINOR_NUMBER_INTEGER_DIGITS\u003c/tt\u003e indefinitely. \u003ctt\u003e_textBuffer.expandCurrentSegment()\u003c/tt\u003e grows the accumulator on every chunk while \u003ctt\u003evalidateIntegerLength()\u003c/tt\u003e is never called. The accumulator is bounded only by \u003ctt\u003emaxStringLength\u003c/tt\u003e (20 MiB by default) rather than by \u003ctt\u003emaxNumberLength\u003c/tt\u003e (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java \u003ctt\u003echar\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eThe equivalent fraction-path code is correct: \u003ctt\u003e_finishFloatFraction()\u003c/tt\u003e calls \u003ctt\u003e_setFractLength()\u003c/tt\u003e before its \u003ctt\u003eNOT_AVAILABLE\u003c/tt\u003e return. The missing call affects the integer-digit paths in \u003ctt\u003e_startPositiveNumber()\u003c/tt\u003e, \u003ctt\u003e_startNegativeNumber()\u003c/tt\u003e and \u003ctt\u003e_finishNumberIntegralPart()\u003c/tt\u003e in \u003ctt\u003eNonBlockingUtf8JsonParserBase\u003c/tt\u003e.\u003c/p\u003e\u003cp\u003e\u003cb\u003eImpact:\u003c/b\u003e 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 \u003ctt\u003eStreamReadConstraints.maxNumberLength\u003c/tt\u003e 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 (\u003ctt\u003eUTF8StreamJsonParser\u003c/tt\u003e, \u003ctt\u003eReaderBasedJsonParser\u003c/tt\u003e) and the async parser operating on complete input are not affected.\u003c/p\u003e\u003cp\u003eExploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed.\u003c/p\u003e\u003cp\u003eThis issue affects \u003ctt\u003ecom.fasterxml.jackson.core:jackson-core\u003c/tt\u003e from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and \u003ctt\u003etools.jackson.core:jackson-core\u003c/tt\u003e from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because \u003ctt\u003eStreamReadConstraints\u003c/tt\u003e -- which defines the \u003ctt\u003emaxNumberLength\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eThe 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).\u003c/p\u003e"
                }
              ],
              "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 \u0027.\u0027 or \u0027e\u0027/\u0027E\u0027 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\u003cDataBuffer\u003e 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"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.