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.
You should upgrade to version 6.0.0 of the provider to avoid even that risk.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Mon, 09 Mar 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 09 Mar 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Airflow Providers Http: Unsafe Pickle Deserialization in apache-airflow-providers-http leading to RCE via HttpOperator | |
| Weaknesses | CWE-913 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-03-09T10:20:47.131Z
Reserved: 2025-12-29T17:02:57.792Z
Link: CVE-2025-69219
No data.
Status : Received
Published: 2026-03-09T11:16:05.907
Modified: 2026-03-09T11:16:05.907
Link: CVE-2025-69219
No data.
OpenCVE Enrichment
No data.
Weaknesses