Skip to content
Fencer Vulns
high 8.4

CVE-2024-56373 json

Apache Airflow: SSTI to Code Execution in Airflow through Shared DB Information

published 2026-02-24 8 mo ago modified 2026-09-10 1 mo ago also BIT-airflow-2024-56373 , EUVD-2024-55432 , GHSA-r837-hpv7-pc2f , PYSEC-2026-2355

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi apache-airflow 2.11.1
  • bitnami airflow 2.11.1
  • Apache Software Foundation Apache Airflow 2.11.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
8 mo ago

Exploit prediction

1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
GitHub 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
CNA 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
OSV 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi apache-airflow
<2.11.1
2.11.1
bitnami airflow
<2.11.1
2.11.1

Affected products

  • Apache Software Foundation Apache Airflow

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.