CVE-2025-69219: Apache Airflow Providers Http: Unsafe Pickle Deserialization in apache-airflow-providers-http leading to RCE via HttpOperator
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.
Users should upgrade to version 6.0.0 of the provider to avoid even that risk.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/apache-airflow-providers-httpto a version that resolves this vulnerability.Fixed in 6.0.0 - Upgrade
Upgrade
apache-airflow-providers-httpto a version that resolves this vulnerability.Fixed in 6.0.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-69219?
CVE-2025-69219 has been rated as critical due to its potential for remote code execution.
How do I fix CVE-2025-69219?
To mitigate CVE-2025-69219, upgrade apache-airflow-providers-http to version 6.0.0 or later.
What does CVE-2025-69219 exploit?
CVE-2025-69219 exploits unsafe pickle deserialization in the HttpOperator of Apache Airflow.
Who is affected by CVE-2025-69219?
Any user with access to the database of an affected Apache Airflow installation is at risk from CVE-2025-69219.
What is the potential impact of CVE-2025-69219?
The potential impact of CVE-2025-69219 is remote code execution, allowing attackers to execute arbitrary code on the Triggerer.