CVE-2026-1518
lowrejectedpriority · track · 0DEEUUSRejected reason: DO NOT USE THIS CANDIDATE NUMBER. After further review by the Keycloak project and Red Hat, the reported SSRF via client registration/backchannel notification URIs was determined not to constitute a security vulnerability. The reported behavior is expected administrator-controlled functionality, and Keycloak provides documented mitigations through Client Policies, including the Secure Client URIs Pattern executor. Therefore, this CVE has been rejected.
cvss
Technical severity, 0–10. One row per scoring source.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-0288Keycloakb (CIBA): Schwachstelle ermöglicht Manipulation von DateienDeutsch2026-02-02csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Keycloak ausnutzen, um Server-Side Request Forgery (SSRF) durchzuführen.
- GHSA-fwhw-chw4-gh37Keycloak Server-Side Request Forgery (SSRF) vulnerability2026-02-02ghsa · osvUS
A flaw was found in Keycloak’s CIBA feature where insufficient validation of client-configured backchannel notification endpoints could allow blind server-side requests to internal services.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (3) cnnvd
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan