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: ghsa, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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)
EPSS
37.3%
KEV
Not listed

Published

March 5, 2026

Last Modified

June 30, 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

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

Vendor Advisories for CVE-2026-3047(2)

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

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

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 8× in last 7d / 12× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 04:40 UTCEG score recompute
  10. 2026-06-30 04:40 UTCVendor advisory
  11. 2026-06-30 04:40 UTCGHSA enrichment
  12. 2026-06-30 04:31 UTCNVD updatefirst tracked

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 June 30, 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 37.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs