jackson-core: ReDoS: quadratic backtracking in NumberInput.PATTERN_FLOAT via looksLikeValidNumber() (CVE-2026-89407)
Published Last modified Sources: Red Hat, CVE.org, OSV, Hersteller, BSI, SUSE
What is affected, what to do
A flaw was found in jackson-core. An attacker can supply specially crafted JSON that, when deserialized into a numeric target type, triggers a Regular expression Denial of Service (ReDoS) vulnerability.
An exploit is publicly available. Update JobScheduler to version 2.8.5.
- Affected
- FasterXML Jackson-core
lte 2.17.0..2.18.10 - FasterXML Jackson-core
lte 2.19.0..2.21.6 - FasterXML Jackson-core
lte 2.22.0..2.22.2 - FasterXML Jackson-core
lte 3.0.0..3.1.6 - FasterXML Jackson-core
lte 3.2.0..3.2.1
- FasterXML Jackson-core
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, CVE.org, OSV, Hersteller, BSI, SUSE
0.6 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 50.1
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- 85.54 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- PoC (publicly reported)
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- 50.1
- 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
- CISA assessment (SSVC)
- Exploitation: proof of concept · automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 22 September 2026
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-1333, CWE-400
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-core. An attacker can supply specially crafted JSON that, when deserialized into a numeric target type, triggers a Regular expression Denial of Service (ReDoS) vulnerability. This occurs due to quadratic backtracking in the NumberInput.looksLikeValidNumber() method's PATTERN_FLOAT regular expression. A small number of concurrent requests with a long input string can exhaust a server's request-handling thread pool, leading to a Denial of Service (DoS).
Source: redhat_csaf, NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities), GitHub Security Advisories, BSI WID Portal, BSI CSAF, suse_csaf
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| FasterXML | jackson-core |
|
|
| SOS GmbH | JobScheduler |
|
|
| maven | com.fasterxml.jackson.core:jackson-core |
|
|
| maven | tools.jackson.core:jackson-core |
|
|
Vendors and products
Weakness classes (CWE)
CWE-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-1333CWE-400Uncontrolled Resource Consumption
Class
The product does not properly control the allocation and maintenance of a limited resource.
Entry at MITRE CWE-400
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CIRCL Sightings | github.com (opens in a new tab) | PoC (publicly reported)reported, not verified |
References & sources
- github.comGHSA-p6pp-m3f8-5c89Vendor advisory
- github.comFasterXML/jackson-core#1649Issue tracking
- github.comFasterXML/jackson-core#1650Patch
- github.comFasterXML/jackson-core#1701 (2.18 backport)Patch
- NVD (NIST)vuln/detail/CVE-2026-89407advisory
- github.comFasterXML/jackson-core/commit/731e794f62623aa0d86ced52490166be9…web
- github.comFasterXML/jackson-core/commit/e7acd64cc99bd346704423dc2bfea1ab0…web
- github.comFasterXML/jackson-corepackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: proof of concept, automatable: yes
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/FasterXML/jackson-core/security/advisories/GHSA-p6pp-m3f8-5c89SSVC assessment added —{"id":"CVE-2026-89407","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-22T15:52:15.349840Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Received36c7be3b…
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness type: CWE-400, CWE-1333
Description added or changed
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —NumberInput.looksLikeValidNumber() in FasterXML jackson-core pre-validates "stringified numbers" with two regular expressions: PATTERN_FLOAT ([+-]?[0-9]*[\.]?[0-9]+([eE][+-]?[0-9]+)?), present since 2.17.0, and PATTERN_FLOAT_TRAILING_DOT, added in 2.17.2. PATTERN_FLOAT places adjacent quantifiers over the same character class -- an optional [0-9]* run, an optional dot, then a required [0-9]+ run -- so input that ultimately fails to match forces Java's backtracking engine to retry every possible split point of the digit run. Matching cost therefore grows with the square of the input length. An attacker who can supply JSON that an application deserializes into a numeric target type reaches this method through jackson-databind's default String-to-number coercion (StdDeserializer and NumberDeserializers for BigDecimal, BigInteger, Double and Float). Because StreamReadConstraints.maxStringLength defaults to 20,000,000 characters, no constraint bounds the input before it reaches the regex. Testing by the reporter confirmed O(n^2) growth across five consecutive input-size doublings, with a single 160,000-character string consuming roughly 74 seconds in one call; a small number of concurrent requests of ordinary body size can therefore exhaust a server's request-handling thread pool. The affected method does not exist before 2.17.0, so 2.16.x and earlier releases are not affected. The fix replaces both regular expressions with a hand-rolled single-pass scan.CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWeakness type (CWE) added —CWE-400Weakness type (CWE) added —CWE-1333Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/89xxx/CVE-2026-89407.json">CVE-2026-89407</a>Reference added —https://github.com/FasterXML/jackson-core/issues/1649Reference added —https://github.com/FasterXML/jackson-core/pull/1650Reference added —https://github.com/FasterXML/jackson-core/pull/1701Reference added —https://github.com/FasterXML/jackson-core/security/advisories/GHSA-p6pp-m3f8-5c89Source identifier: 36c7be3b-2937-45df-85ea-ca7133ea542c
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-89407"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-89407.svg?lang=en" alt="CVE-2026-89407 – NEOSEC Intel" height="20"></a>