# CVE-2026-25604: Apache Airflow AWS Auth Manager - Host Header Injection Leading to SAML Authentication Bypass

> Attackers can bypass SAML authentication in Apache Airflow AWS Auth Manager by manipulating the Host header to access unauthorized instances.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** CLEANSTART-2026-FR48462, ECHO-909d-8f32-2a00, GHSA-rv5f-ccpm-xjj4, MINI-32gr-f528-m85r, MINI-3wqp-6758-c96v, PYSEC-2026-2363

## What is CVE-2026-25604?

CVE-2026-25604 is a medium-severity authentication bypass vulnerability in Apache Airflow Providers Amazon, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-25604?

3 open source packages ship an affected version, including apache-airflow-providers-amazon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow-providers-amazon` | PyPI | All versions | 9.22.0 |
| `apache-airflow-providers-amazon` | PyPI | All versions | 9.22.0 |
| `apache-airflow-providers-amazon` | PyPI | All versions | 9.22.0 |

Products: Apache Apache-Airflow-Providers-Amazon.

## How do I fix CVE-2026-25604?

Upgrade apache-airflow-providers-amazon to 9.22.0 or later.

## Is CVE-2026-25604 being exploited?

There is no known exploitation of CVE-2026-25604 in the wild and no public exploit code.

Public exploit code:

- A PoC for demonstrating CVE-2026-25604 (github_poc): https://github.com/John-Jung/CVE-2026-25604-PoC

## Other vulnerabilities in Apache Airflow Providers Amazon

- [CVE-2023-25956](https://insights.sbomify.com/CVE-2023-25956/): Apache Airflow AWS Provider: Arbitrary file read via AWS provider (high 7.5)
- [CVE-2026-68872](https://insights.sbomify.com/CVE-2026-68872/): Missing authorization in Apache Airflow Amazon provider (medium 6.5)
- [CVE-2026-42526](https://insights.sbomify.com/CVE-2026-42526/): Apache Airflow Amazon provider: Prevent unauthorized access to team-scoped secrets in AWS Secrets Manager and SSM Parameter Store backends (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25604 and fix it if it is affected.

What it is: CVE-2026-25604 is a medium-severity authentication bypass vulnerability in Apache Airflow Providers Amazon, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25604 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow-providers-amazon (PyPI): affected all versions; fixed in 9.22.0
- apache-airflow-providers-amazon (PyPI): affected all versions; fixed in 9.22.0
- apache-airflow-providers-amazon (PyPI): affected all versions; fixed in 9.22.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25604/ (Markdown: https://insights.sbomify.com/CVE-2026-25604/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25604
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25604
- OSV: https://osv.dev/vulnerability/CVE-2026-25604

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25604/
Summaries are generated and may contain mistakes; the official description above is the record.