CVE-2026-25604: Apache Airflow Providers Amazon · Origin Validation Error
Affects Apache Airflow Providers AmazonSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 9.22.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.22.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Apache Airflow Providers Amazon to 9.22.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Airflow Providers Amazon | Affected
| Fixed in
|
PyPIapache-airflow-providers-amazonpkg:pypi/apache-airflow-providers-amazonOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-25604, organizations should immediately upgrade the Apache Airflow Providers Amazon package to version 9.22.0 or later, where the origin validation flaw has been corrected. Beyond patching, organizations should audit their Airflow deployments to identify any unauthorized access or suspicious authentication activity that may have occurred prior to patching. Implement strict network segmentation and access controls to limit exposure of Airflow instances, especially in multi-tenant or multi-instance environments. Review and tighten SAML authentication configurations, ensuring that identity providers and service providers enforce strict origin and audience validation. Employ monitoring and alerting on authentication anomalies and cross-instance access attempts. Consider additional compensating controls such as multi-factor authentication (MFA) for Airflow access and regular security reviews of workflow permissions. Finally, maintain an up-to-date inventory of Airflow instances and their authentication configurations to facilitate rapid response to any future vulnerabilities.
Description
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.