CVE-2026-2603

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. A remote attacker could bypass security controls by sending a valid SAML response from an external Identity Provider (IdP) to the Keycloak SAML endpoint for IdP-initiated broker logins. This allows the attacker to complete broker logins even when the SAML Identity Provider is disabled, leading to unauthorized authentication.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

Published

March 18, 2026

Last Modified

August 18, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3948
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3947
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3926
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3925
redhat

2440300 – (CVE-2026-2603) CVE-2026-2603 keycloak: Keycloak: Unauthorized authentication via disabled SAML Identity Provider

https://bugzilla.redhat.com/show_bug.cgi?id=2440300
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-2603

Vendor Advisories for CVE-2026-2603(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-rhel9-operator:26.4-122026-03-05redhat
redhatrhbk/keycloak-rhel92026-03-05redhat
redhatrhbk/keycloak-rhel9-operator:26.2-162026-03-05redhat

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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.keycloak:keycloak-server-spi-private10.0.0 ... 9.0.3 (161 versions)
  • every version up to 26.5.5: fixed in 26.5.5
—
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (221 versions)
  • every version up to 26.5.5: fixed in 26.5.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 202 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-2603?
CVE-2026-2603 is a high vulnerability published on March 18, 2026. A flaw was found in Keycloak. A remote attacker could bypass security controls by sending a valid SAML response from an external Identity Provider (IdP) to the Keycloak SAML endpoint for IdP-initiated broker logins. This allows the attacker to complete broker logins even when the SAML Identity…
When was CVE-2026-2603 disclosed?
CVE-2026-2603 was first published on March 18, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2603 actively exploited?
CVE-2026-2603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2603?
CVE-2026-2603 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-2603?
A fix for CVE-2026-2603 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2603 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-2603

Explore →

Is Your Infrastructure Affected by CVE-2026-2603?

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

Book a Demo →Browse All CVEs