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%CVSS: 8.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
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 / EcosystemFixed in / 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-samlghsa

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 rangeFixed inDependents
org.keycloak:keycloak-broker-saml1.2.0.Beta1 ... 1.8.1.Final (19 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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 129 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-03 00:00 UTCOSV refresh
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 12:25 UTCEG score recompute
  9. 2026-08-16 12:25 UTCVendor advisory
  10. 2026-08-16 12:25 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 20:48 UTCVendor advisory
  14. 2026-08-14 20:48 UTCGHSA enrichment
  15. 2026-08-14 08:22 UTCEG score recompute
  16. 2026-08-14 08:22 UTCVendor advisory
  17. 2026-08-14 08:22 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 23:57 UTCEG score recompute
  20. 2026-08-12 23:57 UTCVendor advisory
  21. 2026-08-12 23:57 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 22:41 UTCEG score recompute
  24. 2026-08-11 22:41 UTCVendor advisory
  25. 2026-08-11 22:40 UTCGHSA enrichment
  26. 2026-08-11 13:43 UTCEPSS rescore
  27. 2026-08-11 05:28 UTCEG score recompute
  28. 2026-08-11 05:28 UTCVendor advisory
  29. 2026-08-11 05:28 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 07:27 UTCVendor advisory
  32. 2026-08-10 07:27 UTCGHSA enrichment
  33. 2026-08-09 19:24 UTCEG score recompute
  34. 2026-08-09 19:24 UTCVendor advisory
  35. 2026-08-09 19:24 UTCGHSA enrichment
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 08:01 UTCEG score recompute
  38. 2026-08-09 08:01 UTCVendor advisory
  39. 2026-08-09 08:01 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 07:02 UTCVendor advisory
  42. 2026-08-08 07:02 UTCGHSA enrichment
  43. 2026-08-07 19:39 UTCEG score recompute
  44. 2026-08-07 19:39 UTCVendor advisory
  45. 2026-08-07 19:39 UTCGHSA enrichment
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 02:29 UTCEG score recompute
  48. 2026-08-06 02:29 UTCVendor advisory
  49. 2026-08-06 02:29 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-04 02:01 UTCEG score recompute
  54. 2026-08-04 02:01 UTCVendor advisory
  55. 2026-08-04 02:01 UTCGHSA enrichment
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 18:42 UTCEG score recompute
  58. 2026-08-02 18:42 UTCVendor advisory
  59. 2026-08-02 18:42 UTCGHSA enrichment
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-24 14:17 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:08 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-3047?
CVE-2026-3047 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-3047?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3047, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.