Skip to content
Fencer Intel
no cvss —

CVE-2026-1518 json

DO NOT USE THIS CANDIDATE NUMBER.

published 9mo ago modified 3mo ago

Withdrawn or rejected on

Its source no longer considers this a valid vulnerability. It stays here so links keep working, and it is left out of feeds.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Is CVE-2026-1518 in your stack? 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-1518 updated cvss 2.7

keycloak: Blind Server-Side Request Forgery (SSRF) via CIBA Backchannel Notification Endpoint in Keycloak

  • Red Hat Build of Keycloak rhbk/keycloak-rhel9-operator, rhbk/keycloak-operator-bundle
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Build of Keycloak rhbk/keycloak-rhel9
    not affected: vulnerable code cannot be controlled by adversary

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Sources

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.