CVE-2025-69219
Code Injection via Malicious DB Entries in Apache Airflow Triggerer
Publication date: 2026-03-09
Last updated on: 2026-03-10
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | airflow_providers_http | From 5.1.0 (inc) to 6.0.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-913 | The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-69219 is a security vulnerability in the Apache Airflow Providers Http package versions 5.1.0 up to but not including 6.0.0. It involves an unsafe pickle deserialization flaw within the HttpOperator component. A user with access to the Airflow database can craft a malicious database entry that, when processed by the Triggerer service, results in arbitrary code execution. This means that anyone with database access can gain the same permissions as a DAG author.
However, since direct database access is uncommon and not recommended in Airflow deployments, the practical risk of this vulnerability causing damage is considered low.
The vulnerability is addressed by upgrading to version 6.0.0 or later of the apache-airflow-providers-http package, which replaces the insecure pickle serialization with safer JSON serialization for HTTP trigger responses.
How can this vulnerability impact me? :
If exploited, this vulnerability allows an attacker with access to the Airflow database to execute arbitrary code on the Triggerer service. This effectively grants the attacker the same permissions as a DAG author, potentially allowing them to manipulate workflows or perform unauthorized actions within Airflow.
However, because direct database access is not common and is generally discouraged in Airflow environments, the likelihood of this vulnerability being exploited to cause harm is low.
To avoid this risk, it is recommended to upgrade to version 6.0.0 or later of the apache-airflow-providers-http package, which mitigates the vulnerability by changing the serialization method.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2025-69219 vulnerability, you should upgrade the apache-airflow-providers-http package to version 6.0.0 or later.
This update replaces the unsafe pickle serialization used in HTTP triggers with a safer JSON serialization method, eliminating the risk of remote code execution via crafted database entries.
Additionally, since direct database access is uncommon and not recommended in Airflow deployments, limiting or restricting direct DB access further reduces risk.