EM-20261106-5VX1
VulnerabilityMedium severity
SAML Vulnerability (CVE-2026-92856)
CVE-2026-92856
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 05 00:00 UTCC41 Red Hat Security Data
- Page Born
- Nov 06 06:30 UTCsecond source joined
- Last Signal
- Nov 06 06:30 UTC2 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 32 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 06 06:16 UTCC6 NVD published
- Scored: reachedNov 06 06:16 UTCCVSS 4.9
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 05 00:00 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-p9f7-q656-992q / CVE-2026-92856 (opens source in a new tab) A flaw was found in the SAML brokering component of Keycloak, an identity and access management solution. The issue occurs when Keycloak acts as an intermediary between an upstream identity provider and downstream… Med severityDatabaseC29 CIRCL Vulnerability-Lookup
- Red Hat: CVE-2026-92856 (moderate) (opens source in a new tab) keycloak-services: keycloak-services: SAML broker ignores ProxyRestriction delegation constraints Med severityVendorC41 Red Hat Security Data