jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS (CVE-2026-68497)
Published Last modified Sources: Red Hat, SUSE, BSI, Hersteller, CVE.org, OSV
What is affected, what to do
A flaw was found in jackson-databind. An unauthenticated attacker can trigger a denial of service (DoS) by exploiting an unbounded numeric parse vulnerability.
Update FasterXML Jackson-databind to version 2.18.10, FasterXML Jackson-databind to version 2.21.6, FasterXML Jackson-databind to version 2.22.2.
- Affected
- FasterXML Jackson-databind
lt 2.0.0..2.18.10 - FasterXML Jackson-databind
lt 2.19.0..2.21.6 - FasterXML Jackson-databind
lt 2.22.0..2.22.2 - FasterXML Jackson-databind
lt 3.0.0..3.1.6 - FasterXML Jackson-databind
lt 3.2.0..3.2.2
- FasterXML Jackson-databind
- Fixed in
- FasterXML Jackson-databind
2.18.10 - FasterXML Jackson-databind
2.21.6 - FasterXML Jackson-databind
2.22.2 - FasterXML Jackson-databind
3.1.6 - FasterXML Jackson-databind
3.2.2
- FasterXML Jackson-databind
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: Red Hat, SUSE, BSI, Hersteller, CVE.org, OSV
0.6 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 46.8
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 82.91 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.6 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 46.8
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-400, CWE-1333
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in jackson-databind. An unauthenticated attacker can trigger a denial of service (DoS) by exploiting an unbounded numeric parse vulnerability. This occurs during the deserialization of `javax.xml.datatype.Duration` or `javax.xml.datatype.XMLGregorianCalendar` fields from JSON strings, where the system processes arbitrarily long numeric components. This can lead to high CPU utilization, potentially saturating server worker threads and making the service unavailable.
Source: redhat_csaf, suse_csaf, BSI CSAF, BSI WID Portal, GitHub Security Advisories, cvelistv5, OSV (Open Source Vulnerabilities), NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| FasterXML | jackson-databind |
|
|
| Oracle | Communications |
|
|
| Oracle | Construction and Engineering |
|
|
| Oracle | Financial Services Applications |
|
|
Weakness classes (CWE)
CWE-400Uncontrolled Resource Consumption
Class
The product does not properly control the allocation and maintenance of a limited resource.
Entry at MITRE CWE-400CWE-1333Inefficient Regular Expression Complexity
Base
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
Entry at MITRE CWE-1333
References & sources
- github.comGHSA-q4xh-88c3-wmh7Third-party advisory
- github.comFasterXML/jackson-databind#6127Patch, Issue tracking
- github.comFix commit (2.x line, forward-merged to the 2.21, 2.22 and 3.x branches)Patch
- NVD (NIST)vuln/detail/CVE-2026-68497advisory
- github.comFasterXML/jackson-databindpackage
- github.comFasterXML/jackson-databind/releases/tag/jackson-databind-2.18.10web
- github.comFasterXML/jackson-databind/releases/tag/jackson-databind-2.21.6web
- github.comFasterXML/jackson-databind/releases/tag/jackson-databind-2.22.2web
- github.comFasterXML/jackson-databind/releases/tag/jackson-databind-3.1.6web
- github.comFasterXML/jackson-databind/releases/tag/jackson-databind-3.2.2web
Reanalysis & status changes
Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.
CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0
- Reference: after https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-q4xh-88c3-wmh7
- SSVC: after {"id":"CVE-2026-68497","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalI…
New CVE Received36c7be3b-2937-45df-85ea-ca7133ea542c
- Description: after jackson-databind binds a JSON string to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) or newXMLGregorianCalendar(value) in CoreXMLDeserializers.Std._deserialize. These deserializers are registered by default with no opt-in, so a plain ObjectMapper or JsonMapper with no polymorphic typing and no special configuration reaches this path. The XML Schema lexical grammar permits numeric components of arbitrary length, which the JDK materializes through the native BigInteger(String) and BigDecimal(String) constructors, both quadratic in digit count. Because the digits sit inside a JSON string token rather than a JSON number token, jackson-core's StreamReadConstraints.maxNumberLength guard never applies; jackson's own NumberDeserializers call validateIntegerLength or validateFPLength before parsing a stringified number, but the XML datatype deserializer omits that pre-check. An unauthenticated attacker can therefore submit a single request of a few megabytes, such as a Duration value consisting of the letter P followed by several million digits and the letter Y, and force tens of seconds to several minutes of single-threaded CPU work; a handful of concurrent requests can saturate a server's worker threads. This affects com.fasterxml.jackson.core:jackson-databind from 2.0.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.
- CVSS V3.1: after AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CWE: after CWE-400
- CWE: after CWE-1333
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-68497"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-68497.svg?lang=en" alt="CVE-2026-68497 – NEOSEC Intel" height="20"></a>