CVE-2026-92855

HIGHPre-NVD 7.47.4
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-117606 (ENISA EUVD) · GHSA-486h-gxch-8c4x (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The highest-value action is to enforce proof of possession for bound keys in SAML identity broker subject-confirmation validation: upgrade to Keycloak 26.4.17 / 26.6.8 (or the corresponding fixed Red Hat builds), which…"

A flaw was found in the SAML identity broker component of Keycloak, which is used to delegate authentication to external identity providers. The issue occurs because the broker fails to verify that a user actually possesses the private key associated with a holder-of-key assertion. An attacker who intercepts a victim signed assertion can replay it to gain unauthorized access and impersonate the victim without needing their private key.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.4%
EPSS %ILE
35th
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.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

November 5, 2026

Last Modified

November 9, 2026

Advisory Details (4)

Auto-updated Nov 6, 2026
Patch available. Sources: redhat.
Red Hat

2535814 – (CVE-2026-92855) CVE-2026-92855 keycloak-services: keycloak-services: SAML broker accepts holder-of-key assertions without proof of key possession

https://bugzilla.redhat.com/show_bug.cgi?id=2535814
Red HatMentions a patch (unverified)

CVE-2026-92855 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-92855
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:95761
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:95760

Vendor Advisories for CVE-2026-92855(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhbk/keycloak-rhel92026-11-06redhat
redhatrhbk/keycloak-rhel9-operator:26.4-302026-11-06redhat
redhatrhbk/keycloak-rhel9-operator:26.6-242026-11-06redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 20× 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.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-11-09 23:48 UTCEchelonGraph re-scored
  5. 2026-11-09 23:48 UTCVendor advisory
  6. 2026-11-09 23:48 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  7. 2026-11-09 22:30 UTCEchelonGraph re-scored
  8. 2026-11-09 22:30 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  9. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-11-06 19:52 UTCEchelonGraph re-scored
  13. 2026-11-06 19:52 UTCVendor advisory
  14. 2026-11-06 19:52 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  15. 2026-11-06 17:28 UTCEchelonGraph re-scored
  16. 2026-11-06 17:28 UTCVendor advisory
  17. 2026-11-06 17:28 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  18. 2026-11-06 17:18 UTCEchelonGraph re-scored
  19. 2026-11-06 17:18 UTCVendor advisory
  20. 2026-11-06 17:18 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  21. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-11-06 11:27 UTCEchelonGraph re-scored
  23. 2026-11-06 11:27 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
  24. 2026-11-06 10:28 UTCEchelonGraph re-scored
  25. 2026-11-06 10:28 UTCGHSA enrichmentGHSA-486h-gxch-8c4x · GitHub severity HIGH · GitHub CVSS 7.4
Show 4 more
  1. 2026-11-05 18:27 UTCEchelonGraph re-scored
  2. 2026-11-05 18:04 UTCENISA EUVD ID recordedEUVD-2026-117606 · Source: ENISA EUVD
  3. 2026-11-05 17:24 UTCEchelonGraph re-scoredFirst assessed: 7.4 HIGH
  4. 2026-11-05 17:23 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-92855?
CVE-2026-92855 is a high-severity vulnerability; its CVE record was published on November 5, 2026. A flaw was found in the SAML identity broker component of Keycloak, which is used to delegate authentication to external identity providers. The issue occurs because the broker fails to verify that a user actually possesses the private key associated with a holder-of-key assertion. An attacker who…
When was CVE-2026-92855 made public?
CVE-2026-92855 was made public on November 5, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 5, 2026. EchelonGraph's copy of the record carries a last-modified date of November 9, 2026; the record at its source may have been updated since.
Is CVE-2026-92855 actively exploited?
CVE-2026-92855 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92855?
CVE-2026-92855 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92855?
A fix for CVE-2026-92855 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The highest-value action is to enforce proof of possession for bound keys in SAML identity broker subject-confirmation validation: upgrade to Keycloak 26.4.17 / 26.6.8 (or the corresponding fixed Red Hat builds), which…" The vendor advisories EchelonGraph has for CVE-2026-92855 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92855

Explore →

Is Your Infrastructure Affected by CVE-2026-92855?

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

Book a Demo →Browse All CVEs