CVE-2024-56373: Apache Airflow · Code Injection
Affects Apache AirflowSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 2.11.1 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.11.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Apache Airflow to 2.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Airflow | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2024-56373, organizations should immediately upgrade Apache Airflow to version 2.11.1 or later, where the vulnerable log template history feature is disabled by default. For users requiring log template history functionality, upgrading to Apache Airflow 3 is strongly recommended, as it includes a secure implementation of this feature. Until upgrades are applied, administrators should disable the log template history feature manually if possible. Additionally, restrict DAG author permissions to the minimum necessary and audit DAG code for suspicious or unauthorized modifications. Implement network segmentation and firewall rules to limit access to the Airflow web server. Regularly monitor logs for unusual activity related to historical task log access. Employ application-layer security controls such as web application firewalls (WAFs) to detect and block suspicious payloads targeting log rendering. Finally, maintain an incident response plan to quickly address any signs of exploitation.
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.