How to Fix CVE-2026-3047: Authentication bypass by primary weakness in Red Hat build of Keycloak 26.2
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-3047 is a authentication bypass by primary weakness in Red Hat Red Hat build of Keycloak 26.2. The fix is to upgrade to Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1.
| Severity | 8.8 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | See vendor advisory |
| Fixed in | Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1 |
| Type (CWE) | CWE-305: Authentication Bypass by Primary Weakness |
What is CVE-2026-3047?
A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions. The CVSS base score is 8.8 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://access.redhat.com/errata/RHSA-2026:3925.
Am I affected?
Check the version of Red Hat build of Keycloak 26.2 you are running and compare it against the Affected row above (See vendor advisory). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s red-hat-build-of-keycloak-26-2 2>/dev/null | grep -i ^Version
rpm -q red-hat-build-of-keycloak-26-2 2>/dev/null
command -v red-hat-build-of-keycloak-26-2 >/dev/null && red-hat-build-of-keycloak-26-2 --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*Red Hat build of Keycloak 26.2*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Red Hat build of Keycloak 26.2" 2>$null
How to fix CVE-2026-3047
Upgrade Red Hat build of Keycloak 26.2 to a patched build: Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1. The vendor advisory is the source of truth for the exact fixed version.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade red-hat-build-of-keycloak-26-2
dpkg -s red-hat-build-of-keycloak-26-2 | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh red-hat-build-of-keycloak-26-2 -y
# or for older releases:
sudo yum update red-hat-build-of-keycloak-26-2 -y
rpm -q red-hat-build-of-keycloak-26-2
SUSE / openSUSE
sudo zypper refresh
sudo zypper update red-hat-build-of-keycloak-26-2
rpm -q red-hat-build-of-keycloak-26-2
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-3047 affecting Red Hat build of Keycloak 26.2
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-3047-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detect installed version"
$pkg = Get-Package -Name "*Red Hat build of Keycloak 26.2*" -ErrorAction SilentlyContinue
if ($pkg) { $pkg | Format-Table Name, Version }
else { Write-Host "Not detected via Get-Package; try winget list" }
Write-Host "[2/4] Backup configuration"
$backup = "C:\Backup\red-hat-build-of-keycloak-26-2-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\Red Hat build of Keycloak 26.2" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1"
winget upgrade --name "Red Hat build of Keycloak 26.2" --silent --accept-source-agreements --accept-package-agreements
if ($LASTEXITCODE -ne 0) {
# Fallback: pull latest via OS update channel
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verify the patched build"
winget list --name "Red Hat build of Keycloak 26.2"
Write-Host "Patch applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-3047 affecting Red Hat build of Keycloak 26.2
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-3047-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
dpkg -s red-hat-build-of-keycloak-26-2 2>/dev/null | grep -i ^Version || echo "red-hat-build-of-keycloak-26-2 not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q red-hat-build-of-keycloak-26-2 || echo "red-hat-build-of-keycloak-26-2 not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3047-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/red-hat-build-of-keycloak-26-2 /etc/red-hat-build-of-keycloak-26-2.d /etc/red-hat-build-of-keycloak-26-2.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Apply the upgrade (target: Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y red-hat-build-of-keycloak-26-2
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y red-hat-build-of-keycloak-26-2
elif command -v yum >/dev/null; then
yum update -y red-hat-build-of-keycloak-26-2
elif command -v zypper >/dev/null; then
zypper --non-interactive update red-hat-build-of-keycloak-26-2
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s red-hat-build-of-keycloak-26-2 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q red-hat-build-of-keycloak-26-2
fi
echo "Done. Restart any service that loaded the old library."
If you can't patch immediately
Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.
Restrict exposure with nftables (Linux)
# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Block at the host firewall (Windows)
New-NetFirewallRule -DisplayName "Block-CVE-2026-3047" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3047"
Disable the affected service (Linux)
sudo systemctl stop red-hat-build-of-keycloak-26-2 2>/dev/null || true
sudo systemctl disable red-hat-build-of-keycloak-26-2 2>/dev/null || true
If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.
How to verify the fix worked
After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.
# Linux
dpkg -s red-hat-build-of-keycloak-26-2 2>/dev/null | grep -i ^Version
rpm -q red-hat-build-of-keycloak-26-2 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true
# Windows
Get-Package -Name "*Red Hat build of Keycloak 26.2*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above Red Hat build of Keycloak 26.2 26.2-16; Red Hat build of Keycloak 26.2 26.2.14-1; Red Hat build of Keycloak 26.4 26.4-12; Red Hat build of Keycloak 26.4 26.4.10-1. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-44115: Incomplete List of Disallowed Inputs in OpenClaw — Incomplete List of Disallowed Inputs in OpenClaw
- How to Fix CVE-2026-1690: Command Injection in HG10 — Command Injection in HG10
- How to Fix CVE-2026-30496: Improper Authorization in the affected product , Improper Authorization in the affected product
- How to Fix CVE-2026-5124: Access Control Bypass in GoBGP , Access Control Bypass in GoBGP
- How to Fix CVE-2026-44670: Cross-Site Scripting in siyuan , Cross-Site Scripting in siyuan
Is CVE-2026-3047 actively exploited?
There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.
Do I need to reboot after patching CVE-2026-3047?
For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.
What is the CVSS score for CVE-2026-3047?
8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Where is the official advisory for CVE-2026-3047?
The vendor advisory is at https://access.redhat.com/errata/RHSA-2026:3925. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3047.
References
- Official vendor advisory: https://access.redhat.com/errata/RHSA-2026:3925
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3047
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://access.redhat.com/errata/RHSA-2026:3926
- Additional reference: https://access.redhat.com/errata/RHSA-2026:3947
- Additional reference: https://access.redhat.com/errata/RHSA-2026:3948
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*