● Medium · CVSS 5.8

How to Fix CVE-2026-1180: Critical Vulnerability in Red Hat build of Keycloak 26.4

Q: Is CVE-2026-1180 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-1180?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Red Hat build of Keycloak 26.4 run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-44073: Arbitrary File Read in Netatalk — Arbitrary File Read in Netatalk
How to Fix CVE-2026-8262: Cross Site Scripting in ERP Online — Cross Site Scripting in ERP Online
How to Fix CVE-2026-23889: Path Traversal in pnpm , Path Traversal in pnpm
How to Fix CVE-2026-30703: n/a in n/a , n/a in n/a
How to Fix CVE-2026-30291: n/a (Bundle Sibling) , n/a (Bundle Sibling)

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 5.8 - Medium
Actively exploited?	Not currently listed in CISA KEV
Affected	Red Hat build of Keycloak 26.4 - see advisory for affected version ranges
Fixed in	26.4.11-1, 26.4-14, 26.4-14
Type (CWE)	CWE-918: Server-Side Request Forgery (SSRF)

What is CVE-2026-1180?

CVE-2026-1180 is a security flaw in Red Hat build of Keycloak 26.4. A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbitrary jwks_uri, which Keycloak then retrieves without validating the destination.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of Red Hat build of Keycloak 26.4 that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

Check your installed Red Hat build of Keycloak 26.4 version against the affected ranges in the vendor advisory linked below. If you cannot determine the version, treat the system as potentially affected and apply the patched build.

Open Red Hat build of Keycloak 26.4's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-1180

The fix is to upgrade Red Hat build of Keycloak 26.4 to version * or later.

Affected versions confirmed in the CVE record:

Red Hat build of Keycloak 26.4 < *

Patch via the OS package manager (Linux)


<!-- enrich_agent_2:v1 -->
# 1. Update the package metadata.
sudo apt update                                  # Debian / Ubuntu
sudo dnf check-update                            # RHEL / Rocky / AlmaLinux / Fedora
sudo zypper refresh                              # openSUSE

# 2. Pull the patched version `*` of Red Hat build of Keycloak 26.4 from Red Hat.
sudo apt install --only-upgrade red-hat-build-of-keycloak-26.4
sudo dnf upgrade red-hat-build-of-keycloak-26.4
sudo zypper update red-hat-build-of-keycloak-26.4

# 3. Restart the affected service so the patched binary is the running binary.
sudo systemctl restart red-hat-build-of-keycloak-26.4 || true

# 4. Verify the running version.
red-hat-build-of-keycloak-26.4 --version

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://access.redhat.com/errata/RHSA-2026:6477

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

Restrict access to the management interface to trusted internal IP addresses only. Block public access at the firewall and require VPN for any remote administration. Apply the patch as soon as a maintenance window allows.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-1180.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-1180 being exploited in the wild?