Apache Airflow Providers Http: Improper Control of Dynamically-Managed Code Resources
CVE-2025-69219 is a high-severity improper control of dynamically-managed code resources vulnerability in Apache Airflow Providers Http from Apache, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 6.0.0 as the first without the flaw, so updating Apache Airflow Providers Http to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache Airflow Providers Http to 6.0.0 or a later version.
- Update Airflow Providers HTTP to 6.0.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Airflow Providers Http | 5.1.0 up to, but not including, 6.0.0 | 6.0.0 |
| Apache | Airflow Providers HTTP | 5.1.0 up to, but not including, 6.0.0 | 6.0.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Dynamically-Managed Code Resources
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.
How developers prevent this class of flaw
- For any externally-influenced input, check the input against an allowlist of acceptable values.
- Refactor the code so that it does not need to be dynamically managed.
More Improper Control of Dynamically-Managed Code Resources vulnerabilities (CWE-913)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/apache/airflow/pull/61662Issue Tracking
Third-party and government advisories
- openwall.com/lists/oss-security/2026/03/09/1Mailing List, Third Party Advisory
Other references
Recent Improper Control of Dynamically-Managed Code Resources vulnerabilities
- 9.9 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.7 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.