CVE-2026-68497

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-76142 (ENISA EUVD) · GHSA-q4xh-88c3-wmh7 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (HeroDevs) states them: "Upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core) or 3.1.6, 3.2.2 (tools.jackson.core)."

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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 11, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit a99b7e74c892 (FasterXML/jackson-databind)

Fix landed in FasterXML/jackson-databind commit a99b7e74c892 — awaiting tagged release

https://github.com/FasterXML/jackson-databind/commit/a99b7e74c8928f43f6975773a8c862c8316178bd
GitHub pull request

Add `StreamReadConstraints` number len constraint to `javax.xml.datatype.XMLGregorianCalendar` and `javax.xml.datatype.Duration` [CVE-2026-68497]

Fix merged in FasterXML/jackson-databind PR #6127 on 2026-07-29 — awaiting tagged release

https://github.com/FasterXML/jackson-databind/pull/6127
GitHub advisoryMentions a patch (unverified)

Duration XMLGregorianCalendar Unbounded Number Parse DoS · Advisory · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-q4xh-88c3-wmh7

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjackson-modules-base-0:2.21.6-1.el9_42026-11-02redhat
redhatopenvox-server-0:8.17.0-1.el9sat2026-10-29redhat
redhatjackson-databind-0:2.21.6-1.el9_2.12026-10-26redhat
redhatdevspaces/pluginregistry-rhel9:17924952122026-10-26redhat
redhatjackson-modules-base-0:2.21.6-1.el9_62026-10-26redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918163162026-10-21redhat
redhatdogtag-pki-0:11.6.0-3.el10_0.12026-10-21redhat
redhatrhoai/odh-trustyai-service-rhel9:17909330942026-10-21redhat
redhatrhoai/odh-trustyai-service-rhel9:17917925252026-10-19redhat
redhatcom.fasterxml.jackson.core/jackson-databind:2.21.7.redhat-000012026-10-15redhat
redhatjackson-modules-base-0:2.21.6-1.el9_82026-10-12redhat
redhatdogtag-pki-0:11.9.0-6.el10_22026-10-08redhat
redhatrh-lightspeed-runtimes/runtimes-agent-init-rhel9:17902027982026-09-29redhat
redhatjackson-databind2026-09-24redhat
mavencom.fasterxml.jackson.core:jackson-databind @ 2.18.10 (fixes >= 2.14.0, < 2.18.10)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.21.6 (fixes >= 2.19.0, < 2.21.6)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.22.2 (fixes >= 2.22.0, < 2.22.2)—ghsa
maventools.jackson.core:jackson-databind @ 3.2.2 (fixes >= 3.2.0, < 3.2.2)—ghsa
maventools.jackson.core:jackson-databind @ 3.1.6 (fixes >= 3.0.0, < 3.1.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
com.fasterxml.jackson.core:jackson-databind2.22.0, 2.22.1
  • 2.14.0 up to 2.18.10: fixed in 2.18.10
  • 2.19.0 up to 2.21.6: fixed in 2.21.6
  • 2.22.0 up to 2.22.2: fixed in 2.22.2
—
tools.jackson.core:jackson-databind3.0.0 ... 3.1.5 (12 versions)
  • 3.2.0 up to 3.2.2: fixed in 3.2.2
  • 3.0.0 up to 3.1.6: fixed in 3.1.6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2, 2.14.0-1, 2.14.0-1+deb12u1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-1+deb13u1, 2.14.0+ds-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 12× in last 7d / 66× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 127 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 22:05 UTCEG score recompute
  2. 2026-11-03 22:05 UTCVendor advisory
  3. 2026-11-03 22:05 UTCGHSA enrichmentGHSA-q4xh-88c3-wmh7 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-q4xh-88c3-wmh7 · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-01 07:40 UTCEG score recompute
  9. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-27 20:24 UTCEG score recompute
  14. 2026-10-27 20:24 UTCVendor advisory
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-25 14:09 UTCEG score recompute
  19. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-20 10:46 UTCEG score recompute
  25. 2026-10-20 10:46 UTCVendor advisory
Show 75 more
  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-18 03:19 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-13 10:06 UTCEG score recompute
  10. 2026-10-13 10:06 UTCVendor advisory
  11. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-12 15:45 UTCEG score recompute
  13. 2026-10-11 22:26 UTCVendor advisory
  14. 2026-10-11 19:30 UTCEG score recompute
  15. 2026-10-11 16:45 UTCEG score recompute
  16. 2026-10-11 14:06 UTCEG score recompute
  17. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-11 10:03 UTCVendor advisory
  19. 2026-10-10 20:30 UTCEG score recompute
  20. 2026-10-10 20:30 UTCVendor advisory
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-10 08:01 UTCEG score recompute
  23. 2026-10-10 08:01 UTCVendor advisory
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-09 19:30 UTCVendor advisory
  26. 2026-10-08 23:32 UTCEG score recompute
  27. 2026-10-08 23:32 UTCVendor advisory
  28. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-10-08 01:41 UTCEG score recompute
  30. 2026-10-08 01:41 UTCVendor advisory
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-10-07 13:20 UTCVendor advisory
  33. 2026-10-07 00:58 UTCEG score recompute
  34. 2026-10-07 00:58 UTCVendor advisory
  35. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  36. 2026-10-06 12:22 UTCVendor advisory
  37. 2026-10-06 00:01 UTCEG score recompute
  38. 2026-10-06 00:01 UTCVendor advisory
  39. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  40. 2026-10-05 11:40 UTCEG score recompute
  41. 2026-10-05 11:40 UTCVendor advisory
  42. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  43. 2026-10-04 23:19 UTCVendor advisory
  44. 2026-10-04 10:57 UTCVendor advisory
  45. 2026-10-03 22:37 UTCEG score recompute
  46. 2026-10-03 22:37 UTCVendor advisory
  47. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  48. 2026-10-03 10:16 UTCVendor advisory
  49. 2026-10-02 19:50 UTCEG score recompute
  50. 2026-10-02 19:50 UTCVendor advisory
  51. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  52. 2026-10-02 07:29 UTCEG score recompute
  53. 2026-10-02 07:29 UTCVendor advisory
  54. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-10-01 19:08 UTCVendor advisory
  56. 2026-10-01 06:41 UTCVendor advisory
  57. 2026-09-30 18:20 UTCEG score recompute
  58. 2026-09-30 18:20 UTCVendor advisory
  59. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-09-30 05:30 UTCVendor advisory
  61. 2026-09-29 17:06 UTCEG score recompute
  62. 2026-09-29 17:06 UTCVendor advisory
  63. 2026-09-29 04:44 UTCEG score recompute
  64. 2026-09-29 04:44 UTCVendor advisory
  65. 2026-09-28 16:22 UTCEG score recompute
  66. 2026-09-28 16:22 UTCVendor advisory
  67. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  68. 2026-09-28 04:01 UTCVendor advisory
  69. 2026-09-27 15:39 UTCEG score recompute
  70. 2026-09-27 15:39 UTCVendor advisory
  71. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  72. 2026-09-27 03:19 UTCEG score recompute
  73. 2026-09-27 03:19 UTCVendor advisory
  74. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  75. 2026-09-26 14:57 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-68497?
CVE-2026-68497 is a high-severity vulnerability; its CVE record was published on September 11, 2026. 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…
When was CVE-2026-68497 made public?
CVE-2026-68497 was made public on August 6, 2026: that is the date its CVE record's CNA, HeroDevs, gives for when the vulnerability was made public. The CVE record itself was published on September 11, 2026. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-68497 actively exploited?
CVE-2026-68497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68497?
CVE-2026-68497 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68497?
A fix for CVE-2026-68497 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (HeroDevs) states them: "Upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core) or 3.1.6, 3.2.2 (tools.jackson.core)." The vendor advisories EchelonGraph has for CVE-2026-68497 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68497

Explore →

Is Your Infrastructure Affected by CVE-2026-68497?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.