CVE-2025-69219: Apache Airflow Providers Http: Unsafe Pickle Deserialization in apache-airflow-providers-http leading to RCE via HttpOperator

Published Mar 9, 2026
·
Updated

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

3 affected componentsFixes available
pypi/apache-airflow-providers-http<6.0.0
pip/apache-airflow-providers-http<6.0.0
6.0.0
Apache Airflow Providers Http>=5.1.0<6.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/apache-airflow-providers-http to a version that resolves this vulnerability.

    Fixed in 6.0.0
  2. Upgrade

    Upgrade apache-airflow-providers-http to a version that resolves this vulnerability.

    Fixed in 6.0.0

Event History

Mar 9, 2026
CVE Published
via MITRE·10:19 AM
Data Sourced
via MITRE·10:19 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:31 PM
Data Sourced
via GitHub·12:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-69219?

CVE-2025-69219 has been rated as critical due to its potential for remote code execution.

2

How do I fix CVE-2025-69219?

To mitigate CVE-2025-69219, upgrade apache-airflow-providers-http to version 6.0.0 or later.

3

What does CVE-2025-69219 exploit?

CVE-2025-69219 exploits unsafe pickle deserialization in the HttpOperator of Apache Airflow.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203