cve.bz

CVE-2026-18401 fasterxml jackson-core

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in fasterxml jackson-core. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in tools.jackson.core:jackson-core 3.1.0.

On this page
The non-blocking (asynchronous) JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints (default: 1000 characters). An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length, leading to excessive memory allocation and potential CPU exhaustion, resulting in a denial of service. The synchronous parser enforces this limit correctly, so the constraint is applied inconsistently depending on which parsing API the application uses. Root cause: the async parsing path in NonBlockingUtf8JsonParserBase and related classes never invokes the number length validation methods. Number parsing methods such as _finishNumberIntegralPart() accumulate digits into the TextBuffer without any length check, then call _valueComplete() to finalize the token. _valueComplete() does not call resetInt() or resetFloat(), which are the methods in ParserBase where validateIntegerLength() and validateFPLength() are performed. Because that validation step is skipped, maxNumberLength is never enforced on the async code path. Impact: an attacker sending a JSON document containing an arbitrarily long number to an application using the async parser (for example a Spring WebFlux or other reactive application) can cause unbounded allocation in the TextBuffer and an OutOfMemoryError. If the application subsequently calls getBigIntegerValue() or getDecimalValue(), the JVM may additionally be tied up in O(n^2) BigInteger parsing, causing CPU-based denial of service. No privileges or user interaction beyond the ability to submit data for parsing are required. This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.5 and from 2.19.0 through 2.21.0, and tools.jackson.core:jackson-core from 3.0.0 through 3.0.x. 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-72hv-8253-57qq records the lower bound of the affected 2.x range as 2.0.0.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-08-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • tools.jackson.core:jackson-core (Maven): fixed in 3.1.0
  • com.fasterxml.jackson.core:jackson-core (Maven): fixed in 2.21.1, 2.18.6
  • SUSE, openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-18401 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18401?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18401?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18401 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
FasterXML jackson-corefrom 2.15.0 through 2.18.5
FasterXML jackson-corefrom 2.19.0 before 2.21.1
FasterXML jackson-corefrom 3.0.0 before 3.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-72hv-8253-57qqMaventools.jackson.core:jackson-core>=3.0.0 <3.1.03.1.0
GHSA-72hv-8253-57qqMavencom.fasterxml.jackson.core:jackson-core>=2.19.0 <2.21.12.21.1
GHSA-72hv-8253-57qqMavencom.fasterxml.jackson.core:jackson-core>=2.15.0 <2.18.62.18.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morejackson-coreno fix listedUBUNTU-CVE-2026-18401
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morejackson-annotations2.18.11-150200.3.28.1SUSE-SU-2026:4394-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morejackson-core2.18.11-150200.3.30.1SUSE-SU-2026:4394-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morejackson-databind2.18.11-150200.3.36.1SUSE-SU-2026:4394-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morejackson-dataformat-xml2.18.11-150200.5.8.1SUSE-SU-2026:4394-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morejackson-dataformats-binary2.18.11-150200.3.29.1SUSE-SU-2026:4394-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0jackson-core, jackson-databind, jackson-annotations2.18.11-160000.1.1SUSE-SU-2026:24149-1
openSUSELeap 16.0jackson-core, jackson-databind, jackson-annotations2.18.11-160000.1.1openSUSE-SU-2026:22034-1
openSUSETumbleweedjackson-core2.18.9-2.1openSUSE-SU-2026:11638-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat's assessment of this vulnerability differs from the reported vendor severity. The flaw exists only in jackson-core's non-blocking (asynchronous) JSON parser, which does not enforce the maxNumberLength constraint defined by StreamReadConstraints. Applications that use the standard, synchronous parsing API (the default for the vast majority of Java applications using jackson-core, including via ObjectMapper) enforce this limit correctly and are not affected by this specific code path. Only applications that explicitly invoke the non-blocking parser API, typically reactive frameworks processing untrusted network input, are exposed to the described memory/CPU exhaustion behavior. Red Hat rates this issue as Moderate.

Red Hat's mitigation

No mitigation is available for applications that use the non-blocking/async parser API with untrusted input. Affected users should upgrade to jackson-core 2.18.6, 2.21.1, 3.1.0, or later. Applications that only use the standard (synchronous) parser API are not affected and require no action.

ProductPackageStateAdvisory
Cryostat 4jackson-coreNot affected
OpenShift Developer Tools and ServicesjenkinsOut of support scope
OpenShift Developer Tools and Servicesjenkins-2-pluginsOut of support scope
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel8Not affected
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel9Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-dispatcher-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-ekb-receiver-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-log-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-timer-source-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-gaudi-rhel9Not affected
Red Hat AMQ Broker 7amq-broker-bin.zipNot affected
Red Hat AMQ Broker 7amq-broker-maven-repository.zipNot affected
Red Hat AMQ Clientsjackson-coreFix deferred
86 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-18401.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON