Keycloak is a widely used identity provider; token forgery enables impersonation and unauthorized access across many enterprise apps and services.
CVE-2026-92857
Keycloak dynamic client registration lets attackers forge tokens to impersonate users
Is CVE-2026-92857 being exploited?
Not confirmed. CVE-2026-92857 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-92857?
CVE-2026-92857 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92857?
Yes. A fix has been recorded for CVE-2026-92857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92857 affect?
CVE-2026-92857 affects Keycloak, Red Hat SSO (downstream), Applications relying on Keycloak-issued tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92857?
Apply vendor update immediately; revoke/rotate affected tokens; audit and restrict client registrations
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can register malicious clients that forge 'sub'/'aud' in signed tokens to impersonate users and gain unauthorized access to services.
Immediate action required
timeline
- 5 Nov 2026Published
- 5 Nov 2026CVE record last updated · same day later
- 6 Nov 2026Analysed by vulneraibility.com · 1 day later
- Linkaccess.redhat.com /security/cve/CVE-2026-92857
- Linkbugzilla.redhat.com /show_bug.cgi?id=2535817
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.