● Medium · CVSS 5.4

How to Fix CVE-2026-25604: CWE-346: Origin Validation Error in Apache Airflow Providers Amazon

Q: Is CVE-2026-25604 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-25604?

CVSS rates it 5.4 (Medium). Use that score to set your patch priority next to the other items in your queue.

Q: Do I have to take Apache Airflow Providers Amazon offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-25604 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

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

How to Fix CVE-2026-40010: Session Fixation in Apache Wicket — Session Fixation in Apache Wicket
How to Fix CVE-2026-35337: Deserialization of untrusted data in Apache Storm Client — Deserialization of untrusted data in Apache Storm Client
How to Fix CVE-2026-33557: Validation of specified index, position, or in Apache Kafka , Validation of specified index, position, or in Apache Kafka
How to Fix CVE-2026-29129: Use of a broken or risky in Apache Tomcat , Use of a broken or risky in Apache Tomcat
How to Fix CVE-2026-29145: Authentication bypass in Apache Tomcat , Authentication bypass in Apache Tomcat

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 5.4, Medium
Actively exploited?	No
Affected	Apache Software Foundation Apache Airflow Providers Amazon (8.0.0 < 9.22.0)
Fixed in	9.22.0
Type (CWE)	CWE-346: Origin Validation Error

What is CVE-2026-25604?

In AWS Auth manager, the origin of the SAML authentication has been used as provided by the client and not verified against the actual instance URL. This allowed to gain access to different instances with potentially different access controls by reusing SAML response from other instances. You should upgrade to 9.22.0 version of provider if you use AWS Auth Manager.

In practical terms, a successful attacker gets compromise of the affected component as described in the vendor advisory. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You're affected if you run Apache Software Foundation Apache Airflow Providers Amazon at any version in the Affected row above. Use these probes to find your installed build:


# Confirm the installed version via your package manager
dpkg -l | grep -i apache   # Debian/Ubuntu
rpm -qa | grep -i apache   # RHEL/CentOS/Rocky

How to fix CVE-2026-25604

The primary fix is to upgrade to the patched build listed in the Fixed in row above (9.22.0). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


sudo apt-get update
sudo apt-get install --only-upgrade apache-airflow-providers-amazon
# Confirm the installed version meets or exceeds 9.22.0
dpkg -s apache-airflow-providers-amazon | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security apache-airflow-providers-amazon -y
rpm -q apache-airflow-providers-amazon

Windows (PowerShell, admin)


# Try winget first
winget upgrade --id 'Apache Software Foundation.Apache Airflow Providers Amazon' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\ApacheAirflowProvidersAmazon-9.22.0.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log


# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\ApacheAirflowProvidersAmazon-Patch-CVE-2026-25604.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-25604 remediation for Apache Software Foundation Apache Airflow Providers Amazon"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Apache*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'9.22.0') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\ApacheAirflowProvidersAmazon-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Apache Software Foundation\Apache Airflow Providers Amazon"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\ApacheAirflowProvidersAmazon-9.22.0.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Apache*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'9.22.0') {
    Write-Log "SUCCESS: now at $verify (>= 9.22.0)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log


#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/apache-airflow-providers-amazon-patch-cve-2026-25604.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-25604 remediation for Apache Software Foundation Apache Airflow Providers Amazon"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s apache-airflow-providers-amazon >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' apache-airflow-providers-amazon)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q apache-airflow-providers-amazon >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' apache-airflow-providers-amazon)
    PKG_MGR=dnf
else
    log "apache-airflow-providers-amazon not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: apache-airflow-providers-amazon=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/apache-airflow-providers-amazon-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/apache-airflow-providers-amazon /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y apache-airflow-providers-amazon
else
    sudo dnf upgrade --security -y apache-airflow-providers-amazon
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' apache-airflow-providers-amazon)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' apache-airflow-providers-amazon)
fi
log "After upgrade: $NEW"

# Optionally compare against 9.22.0 with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

No official vendor workaround is published for this CVE; patching is the only documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.

Restrict the affected service to trusted networks (Linux):


# Vendor advisory: https://github.com/apache/airflow/pull/61368
# Replace <port> with the affected service port and 10.0.0.0/24 with your admin subnet
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP

Windows Firewall equivalent:


# Vendor advisory: https://github.com/apache/airflow/pull/61368
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' \
    -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' \
    -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


apache2 -v   # Debian/Ubuntu
httpd -v     # RHEL/CentOS

Expected output: the Server version line should show the patched build.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-25604 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-25604 being actively exploited?