CVE-2026-3047

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

Published

March 5, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat

2441966 – (CVE-2026-3047) CVE-2026-3047 org.keycloak.broker.saml: Keycloak SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login

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

cve-details

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhbk/keycloak-rhel92026-03-05redhat
redhatrhbk/keycloak-rhel9-operator:26.2-162026-03-05redhat
redhatrhbk/keycloak-rhel9-operator:26.4-122026-03-05redhat
mavenorg.keycloak:keycloak-broker-saml—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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.keycloak:keycloak-broker-saml1.2.0.Beta1 ... 1.8.1.Final (19 versions)
  • every version through 1.8.1.Final: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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 140 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-3047?
CVE-2026-3047 is a high vulnerability published on March 5, 2026. A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This allows a remote…
When was CVE-2026-3047 disclosed?
CVE-2026-3047 was first published on March 5, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3047 actively exploited?
CVE-2026-3047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3047?
CVE-2026-3047 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-3047?
A fix for CVE-2026-3047 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-3047 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-3047

Explore →

Is Your Infrastructure Affected by CVE-2026-3047?

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