CVE-2026-91777

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-30. 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
Elevated

Also known asEUVD-2026-85003 (ENISA EUVD) · GHSA-cxp5-3px4-pw24 (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.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID. The affected paths are CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference() and the equivalent implementation in MapDeserializer. When a document first creates N unresolved object-ID references in an identity-enabled collection or map and then defines those same IDs in reverse order, completion performs on the order of N * (N + 1) / 2 identity comparisons, so a shallow document whose size grows linearly causes quadratic CPU work during deserialization. The reporter instrumented equals() calls on the ID class and measured exactly 2,003,000 comparisons at N = 2,000, against zero comparisons in the pending-reference lookup path for an equally sized control in which every reference was already resolved. The input requires no deep nesting and no syntactically unusual JSON. Exploitation requires an application that deserializes attacker-influenced JSON into an identity-enabled collection or map. The fix replaces the repeated linear lookup with a keyed pending-reference structure.

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.5%
EPSS %ILE
42nd
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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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 23, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 23, 2026
Patch available. Sources: github.
Web page

Avoid quadratic forward-reference resolution in Collection/Map deserializers [CVE-2026-91777] by pjfanning · Pull Request #6204 · FasterXML/jackson-databind · GitHub

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

jackson-databind quadratic forward-reference completion · Advisory · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-cxp5-3px4-pw24

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjackson-databind2026-11-06redhat
redhatrhbk/keycloak-rhel9-operator:26.6-242026-11-06redhat
redhatjackson-modules-base-0:2.21.6-1.el9_42026-11-02redhat
redhatpki-deps:10.6-8100020261021095739.489197e62026-10-27redhat
redhatjackson-modules-base-0:2.21.6-1.el9_62026-10-26redhat
redhatjackson-databind-0:2.21.6-1.el9_2.12026-10-26redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatrhoai/odh-trustyai-service-rhel9:17909330942026-10-21redhat
redhatjackson-databind-0:2.21.6-1.el9_8.12026-10-19redhat
redhatcom.fasterxml.jackson.core/jackson-databind:2.21.7.redhat-000012026-10-15redhat
mavencom.fasterxml.jackson.core:jackson-databind @ 2.21.7 (fixes >= 2.19.0, <= 2.21.6)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.18.11 (fixes >= 2.5.0, <= 2.18.10)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.22.3 (fixes >= 2.22.0, <= 2.22.2)—ghsa
maventools.jackson.core:jackson-databind @ 3.1.7 (fixes >= 3.0.0, <= 3.1.6)—ghsa
maventools.jackson.core:jackson-databind @ 3.2.3 (fixes >= 3.2.0, <= 3.2.2)—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.22.2
  • 2.19.0 up to 2.21.7: fixed in 2.21.7
  • 2.5.0 up to 2.18.11: fixed in 2.18.11
  • 2.22.0 up to 2.22.3: fixed in 2.22.3
—
tools.jackson.core:jackson-databind3.2.0, 3.2.1, 3.2.2
  • 3.0.0 up to 3.1.7: fixed in 3.1.7
  • 3.2.0 up to 3.2.3: fixed in 3.2.3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1 ... 2.18.11-1 (6 versions)
  • 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, 2.14.0+ds-3, 2.18.11-1
  • 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, 2.14.0+ds-3
  • every version up to 2.18.11-1: fixed in 2.18.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

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. 1 repeat row among the latest 90 is merged into the row it repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-10 15:13 UTCEchelonGraph re-scored
  5. 2026-11-10 15:13 UTCVendor advisory
  6. 2026-11-10 15:13 UTCGHSA enrichmentGHSA-cxp5-3px4-pw24 · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-11-03 17:57 UTCEchelonGraph re-scored
  14. 2026-11-03 17:57 UTCVendor advisory
  15. 2026-11-03 17:57 UTCGHSA enrichmentGHSA-cxp5-3px4-pw24 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-cxp5-3px4-pw24 · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-11-01 07:37 UTCEchelonGraph re-scored
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-27 19:29 UTCEchelonGraph re-scored
Show 64 more
  1. 2026-10-27 19:29 UTCVendor advisory
  2. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-25 13:51 UTCEchelonGraph re-scored
  6. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  8. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  9. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-20 07:02 UTCEchelonGraph re-scored
  12. 2026-10-20 07:02 UTCVendor advisory
  13. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-18 03:00 UTCEchelonGraph re-scored
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  17. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-13 04:40 UTCEchelonGraph re-scored
  22. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-10-12 14:45 UTCEchelonGraph re-scored
  24. 2026-10-11 19:13 UTCEchelonGraph re-scored
  25. 2026-10-11 16:30 UTCEchelonGraph re-scored
  26. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  27. 2026-10-11 13:44 UTCEchelonGraph re-scored
  28. 2026-10-11 00:11 UTCEchelonGraph re-scored
  29. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  30. 2026-10-10 02:17 UTCEchelonGraph re-scored
  31. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  32. 2026-10-09 04:06 UTCEchelonGraph re-scored
  33. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  34. 2026-10-08 05:53 UTCEchelonGraph re-scored
  35. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  36. 2026-10-06 21:03 UTCEchelonGraph re-scored
  37. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  38. 2026-10-05 22:40 UTCEchelonGraph re-scored
  39. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  40. 2026-10-05 00:43 UTCEchelonGraph re-scored
  41. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-10-03 15:52 UTCEchelonGraph re-scored
  43. 2026-10-03 04:49 UTCEchelonGraph re-scored
  44. 2026-10-01 20:00 UTCEchelonGraph re-scored
  45. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-30 22:08 UTCEchelonGraph re-scored
  47. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-09-30 00:15 UTCEchelonGraph re-scored
  49. 2026-09-28 23:58 UTCEchelonGraph re-scored
  50. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  51. 2026-09-27 15:08 UTCEchelonGraph re-scored
  52. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  53. 2026-09-26 17:14 UTCEchelonGraph re-scored
  54. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  55. 2026-09-26 06:14 UTCEchelonGraph re-scored
  56. 2026-09-24 20:55 UTCEchelonGraph re-scored
  57. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  58. 2026-09-24 02:16 UTCEchelonGraph re-scored
  59. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  60. 2026-09-23 15:20 UTCEchelonGraph re-scored
  61. 2026-09-23 14:24 UTCEchelonGraph re-scored
  62. 2026-09-23 03:27 UTCEchelonGraph re-scored
  63. 2026-09-23 02:28 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  64. 2026-09-23 02:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91777?
CVE-2026-91777 is a high-severity vulnerability; its CVE record was published on September 23, 2026. Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID. The affected paths are CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference() and the equivalent…
When was the CVE record for CVE-2026-91777 published?
The CVE record for CVE-2026-91777 was published on September 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-91777 actively exploited?
CVE-2026-91777 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91777?
CVE-2026-91777 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-91777?
A fix for CVE-2026-91777 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91777 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-91777

Explore →

Is Your Infrastructure Affected by CVE-2026-91777?

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