EM-20261105-7T40
VulnerabilityHigh severity
SAML Vulnerability (CVE-2026-92855)
CVE-2026-92855
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 05 00:00 UTCC41 Red Hat Security Data
- Page Born
- Nov 05 18:17 UTCsecond source joined
- Last Signal
- Nov 05 18:17 UTC11 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 25 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 05 18:17 UTCC6 NVD published
- Scored: reachedNov 05 18:17 UTCCVSS 7.4
- 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
- CVE-2026-92855 (CVSS 7.4) (opens source in a new tab) A flaw was found in the SAML identity broker component of Keycloak, which is used to delegate authentication to external identity providers. The issue occurs because the broker fails to verify that a user actually posses… High severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-92855 (important) (opens source in a new tab) keycloak-services: keycloak-services: SAML broker accepts holder-of-key assertions without proof of key possession High severityVendorC41 Red Hat Security Data