Keycloak Server-Side Request Forgery (SSRF) vulnerability

published 2026-02-02 9mo ago modified 2026-02-03 9mo ago also CVE-2026-1518

cvss: 2.7; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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.

Is GHSA-fwhw-chw4-gh37 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	2.7	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.keycloak:keycloak-parent	<=26.5.2	no fix listed

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

nvd.nist.gov /vuln/detail/CVE-2026-1518
advisory
access.redhat.com /security/cve/CVE-2026-1518
web
bugzilla.redhat.com /show_bug.cgi?id=2433727
web
github.com /keycloak/keycloak
package

Sources

GitHub Advisory GHSA-fwhw-chw4-gh37

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.