Is CVE-2026-1518 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-1518 being exploited in the wild.

How severe is CVE-2026-1518?

Low severity, with a CVSS score of 3.1, published 2 February 2026.

Which products and versions are affected?

org.keycloak:keycloak-parent (Maven) ECOSYSTEM:introduced=0,last_affected=26.5.2.

Is there a fix for CVE-2026-1518?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-1518 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-1518?

Check whether you run org.keycloak:keycloak-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-1518: Keycloak SSRF in client registration and backchannel notification URIs

CVE-2026-1518 · Severity: low · CVSS 3.1 · Published 2026-02-02

A reported security issue in Keycloak, an identity and access management solution, was determined to be expected behavior rather than a vulnerability. The report suggested that administrators could configure certain notification addresses to trigger internal network requests, but this is a standard administrative function. Organizations using Keycloak are not at increased risk from this report, as existing security controls already manage this functionality.

Technologies: org.keycloak:keycloak-parent (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-1518 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-1518 being exploited in the wild.
How severe is CVE-2026-1518?: Low severity, with a CVSS score of 3.1, published 2 February 2026.
Which products and versions are affected?: org.keycloak:keycloak-parent (Maven) ECOSYSTEM:introduced=0,last_affected=26.5.2.
Is there a fix for CVE-2026-1518?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-1518 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-1518?: Check whether you run org.keycloak:keycloak-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A potential Server-Side Request Forgery (SSRF) was reported in Keycloak's Client Initiated Backchannel Authentication (CIBA) feature and client registration endpoints. The concern was that insufficient validation of backchannel notification URIs could allow the server to make requests to internal services. However, Red Hat and the Keycloak project determined this is expected behavior for authenticated administrators. Keycloak provides built-in mitigations for this behavior via Client Policies and the 'Secure Client URIs Pattern' executor, leading to the formal rejection of the CVE.

Affected products

Red Hat Keycloak All versions (Rejected)

Identifiers

CVE-2026-1518
GHSA-fwhw-chw4-gh37

Timeline

2026-02-02: disclosed: Initial CVE publication
2026-07-24: other: CVE formally rejected by Red Hat and the Keycloak project

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.