Security readout for executives and security teams
Plain-English summary
CVE-2026-1180 is a blind SSRF flaw in Keycloak’s OIDC Dynamic Client Registration. An attacker can cause Keycloak to request attacker-chosen URLs through jwks_uri. Business risk is mainly internal reconnaissance and limited information disclosure, including possible probing of internal services or cloud metadata endpoints.
Executive priority
Prioritize remediation for internet-facing or partner-facing Keycloak instances with Dynamic Client Registration enabled. Treat as moderate urgency: it can expose internal network information, but supplied sources do not indicate active exploitation or direct system compromise.
Technical view
When OIDC Dynamic Client Registration uses private_key_jwt, Keycloak retrieves a supplied jwks_uri without validating the destination. This is CWE-918 SSRF, CVSS 5.8. The flaw is network-exploitable, low complexity, no privileges, no user interaction, with low confidentiality impact and no integrity or availability impact stated.
Likely exposure
Most relevant to Red Hat build of Keycloak 26.4 deployments using OIDC Dynamic Client Registration with private_key_jwt. Exposure is higher when Keycloak can reach internal networks, restricted services, or cloud metadata endpoints.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation would depend on reachable registration functionality and Keycloak server egress paths. The impact described is blind SSRF for probing or limited disclosure, not direct code execution.
Researcher notes
Affected status is Red Hat-specific in the provided bundle. Some related products are marked unaffected, including JBoss EAP 8, EAP Expansion Pack, and Red Hat Single Sign-On 7 keycloak-services. Verify exact package names and advisory applicability before concluding exposure.
Mitigation direction
- Review Red Hat advisories RHSA-2026:6477 and RHSA-2026:6478 for applicable updates.
- Apply vendor-provided fixed packages where your Red Hat build of Keycloak package is affected.
- Restrict Keycloak outbound network access to only required destinations.
- Review whether OIDC Dynamic Client Registration is required and safely configured.
- Block access from Keycloak to cloud metadata and sensitive internal endpoints where possible.
Validation and detection
- Inventory Red Hat build of Keycloak 26.4 deployments and package variants.
- Compare installed packages against Red Hat CVE and RHSA affected status.
- Confirm whether OIDC Dynamic Client Registration is enabled.
- Identify clients or workflows using private_key_jwt and jwks_uri.
- Review Keycloak egress logs for unexpected internal or metadata endpoint requests.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1180 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
- Medium
- CVSS
- 5.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.8MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:6477CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:6478CVE reference · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-1180CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2430781CVE reference · issue-tracking, x_refsource_REDHAT
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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.