Apache Airflow: Improper Control of Generation of Code
CVE-2024-56373 is a high-severity improper control of generation of code vulnerability in Apache Airflow from Apache, with a CVSS 3.1 base score of 8.4 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. The record lists version 2.11.1 as the first without the flaw, so updating Apache Airflow to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.23% chance of exploitation within 30 days, higher than 69% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache Airflow to 2.11.1 or a later version.
- Update Airflow to 2.11.1 or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Airflow | before 2.11.1 | 2.11.1 |
| Apache | Airflow | before 2.11.1 | 2.11.1 |
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
- HighAdministrator-level access is required first.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- 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:H/UI:R/S:C/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
DAG Author (who already has quite a lot of permissions) could manipulate database of Airflow 2 in the way to execute arbitrary code in the web-server context, which they should normally not be able to do, leading to potentially remote code execution in the context of web-server (server-side) as a result of a user viewing historical task information. The functionality responsible for that (log template history) has been disabled by default in 2.11.1 and users should upgrade to Airflow 3 if they want to continue to use log template history. They can also manually modify historical log file names if they want to see historical logs that were generated before the last log template change.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
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
Advisories
Patches and release notes
- github.com/apache/airflow/pull/61880Issue Tracking
Third-party and government advisories
- openwall.com/lists/oss-security/2026/02/23/3Mailing List, Third Party Advisory
Other vulnerabilities in Apache Airflow
- 8.8 High severity
- 8.8 High severity
- 7.3 High severity
- 9.8 Critical severity
- 8.2 High severity
- 7.5 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 8.6 High severity
- 9.8 Critical severity
- 9.9 Critical severity
- 7.2 High severity
- 9.9 Critical severity
- 7.7 High severity
Spotted an error? Tell us.