CVE-2025-69219 Apache Airflow Providers Http has Unsafe Pickle Deserializatio leading to RCE via HttpOperator
An attacker with database access can trigger remote code execution on the Triggerer via unsafe pickle deserialization in the HTTP provider.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-69219?
CVE-2025-69219 is a high-severity unsafe deserialization vulnerability in Apache Airflow Providers Http, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A user with access to the DB could craft a database entry that would result in executing code on Triggerer - which gives anyone who have access to DB the same permissions as Dag Author. Since direct DB access is not usual and recommended for Airflow, the likelihood of it making any damage is low.
You should upgrade to version 6.0.0 of the provider to avoid even that risk.
Weakness: CWE-913
Which versions are affected by CVE-2025-69219?
3 open source packages ship an affected version, including apache-airflow-providers-http. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
apache-airflow-providers-http PyPI | All versions | 6.0.0 |
apache-airflow-providers-http PyPI | All versions | 6.0.0 |
apache-airflow-providers-http PyPI | All versions | 6.0.0 |
Products include Apache Airflow Providers Http.
How do I fix CVE-2025-69219?
Upgrade apache-airflow-providers-http to 6.0.0 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-69219 being exploited?
There is no known exploitation of CVE-2025-69219 in the wild and no public exploit code.
Public exploit code: 2 proofs of concept on GitHub.
Sources
Also known as CLEANSTART-2026-KP40692, CLSA-2026-1779670115, ECHO-7803-48c3-bfab, GHSA-9r5j-7r2x-rv4g, MINI-8h9q-4vj5-gqmq, MINI-mxj3-mvfm-qmrm and 1 more.