Security readout for executives and security teams
Plain-English summary
Keycloak versions before 12.0.0 allowed unsafe schemes in the redirect_uri parameter, creating a cross-site scripting risk. Because Keycloak is an identity platform, successful abuse could affect users interacting with authentication flows. The provided sources do not include CVSS, patch notes, or evidence of active exploitation.
Executive priority
Handle as a medium-priority identity-platform fix. There is no active exploitation evidence in the supplied sources, but vulnerable Keycloak authentication flows could expose users to XSS.
Technical view
CVE-2020-10776 is a CWE-79 issue in Keycloak before 12.0.0 involving unsafe redirect_uri schemes. The described impact is cross-site scripting. The source bundle does not provide exploit prerequisites, affected configurations, CVSS scoring, or detailed remediation beyond the affected version boundary.
Likely exposure
Organizations running Keycloak before 12.0.0 are potentially exposed. Exposure is most relevant where Keycloak authentication flows are internet-facing or reachable by untrusted users.
Exploitation context
The bundle marks CISA KEV as false and provides no cited evidence of active exploitation. Treat exploit status as unconfirmed, not actively exploited.
Researcher notes
Evidence is sparse. The public bundle identifies Keycloak before 12.0.0, CWE-79, redirect_uri unsafe schemes, and XSS impact, but omits CVSS, exploitation details, and configuration-specific scope.
Mitigation direction
- Inventory all Keycloak deployments and record exact versions.
- Upgrade affected Keycloak instances off versions before 12.0.0.
- Review vendor guidance from Keycloak or Red Hat for supported remediation details.
- Review configured redirect_uri values and remove unsafe or unnecessary schemes.
- Prioritize internet-facing identity services before internal-only deployments.
Validation and detection
- Confirm each Keycloak instance reports version 12.0.0 or later.
- Check client redirect_uri configurations for unsafe schemes.
- Verify public authentication flows still operate after remediation.
- Review identity service exposure for internet-reachable Keycloak endpoints.
- Document any remaining pre-12.0.0 instances as accepted risk or remediation backlog.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-10776 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=1847428CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
