How to Fix CVE-2026-40948: Cross-site request forgery in Apache Airflow Providers Keycloak
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 5.4 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Apache Software Foundation Apache Airflow Providers Keycloak 0.0.1 to <0.7.0 |
| Fixed in | Apache Airflow Providers Keycloak 0.7.0 |
| Type (CWE) | CWE-352: CWE-352: Cross-Site Request Forgery (CSRF) |
What is CVE-2026-40948?
The Keycloak authentication manager in apache-airflow-providers-keycloak did not generate or validate the OAuth 2.0 state parameter on the login / login-callback flow, and did not use PKCE. An attacker with a Keycloak account in the same realm could deliver a crafted callback URL to a victim's browser and cause the victim to be logged into the attacker's Airflow session (login-CSRF / session fixation), where any credentials the victim subsequently stored in Airflow Connections would be harvestable by the attacker. Users are advised to upgrade apache-airflow-providers-keycloak to 0.7.0 or later.
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s apache2 2>/dev/null | grep -i version
rpm -q apache2 2>/dev/null
apache2 --version 2>/dev/null
Compare what you see against the Affected row above (Apache Software Foundation Apache Airflow Providers Keycloak 0.0.1 to <0.7.0). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-40948
The primary fix is to upgrade Apache Airflow Providers Keycloak to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: Apache Airflow Providers Keycloak 0.7.0.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade apache2
apache2 --version 2>/dev/null || dpkg -s apache2 | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security apache2 -y
rpm -q apache2
SUSE / openSUSE
sudo zypper patch --category security
rpm -q apache2
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-40948 affecting Apache HTTP Server
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-40948-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] Detecting installed version of Apache HTTP Server"
$pkg = winget list --id "Apache_HTTP_Server" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\Apache_HTTP_Server-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\Apache_HTTP_Server" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to Apache Airflow Providers Keycloak 0.7.0"
winget upgrade --id "Apache_HTTP_Server" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "Apache_HTTP_Server"
Write-Host "Fix 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-40948 affecting Apache HTTP Server
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-40948-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s apache2 2>/dev/null | grep -i version || echo "apache2 not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q apache2 || echo "apache2 not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-40948-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/apache2 /etc/apache2.d /etc/apache2.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: Apache Airflow Providers Keycloak 0.7.0)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y apache2
elif command -v dnf >/dev/null; then
dnf upgrade --security -y apache2
elif command -v yum >/dev/null; then
yum update -y apache2
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s apache2 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q apache2
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop apache2
sudo systemctl disable apache2
How to verify the fix worked
# Linux
apache2 --version 2>/dev/null || dpkg -s apache2 | grep -i version
rpm -q apache2 2>/dev/null || true
# Windows
winget list | findstr /I "apache2"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above Apache Airflow Providers Keycloak 0.7.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-28367: Critical Vulnerability in Red Hat build of Apache Camel for Spring Boot 4 — Critical Vulnerability in Red Hat build of Apache Camel for Spring Boot 4
- How to Fix CVE-2026-25903: Critical Vulnerability in Apache NiFi — Critical Vulnerability in Apache NiFi
- How to Fix CVE-2026-41873: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') , CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
- How to Fix CVE-2026-33006: Observable Timing Discrepancy in Apache HTTP Server , Observable Timing Discrepancy in Apache HTTP Server
- How to Fix CVE-2026-40023: Encoding or escaping of output in Apache Log4cxx , Encoding or escaping of output in Apache Log4cxx
Is CVE-2026-40948 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
5.4 (medium). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://lists.apache.org/thread/kc0odpr70hbqhdb9ksnz42fkqz2xld9q
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40948
- https://github.com/apache/airflow/pull/64114
- http://www.openwall.com/lists/oss-security/2026/04/17/14
*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.*