CVE-2024-56373

highpriority · track · 0EPSS 0.012 · 69 %ileDEEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

1.23% (69th) EPSS

CVSS 8.4 · high

Is it mine?

6 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · osv · cert_bund

EPSS · scored 2026-10-27

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.

cvss

Technical severity, 0–10. One row per scoring source.

8.4

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.18.4highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Hsecondary · ENISA EU

v3.18.4highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Hsecondaryexploitability 1.7 · impact 6

v3.18.4highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:Hsecondary · OSV

v3.17.7highCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: no · Technical Impact: totalcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-94USCWE-94US

affected products (6)

Products and version ranges known to be affected.

Apache Airflow <2.11.1all versionscert_bundDE
Apache Airflow< 2.11.1cert_bundDE
Apache Software Foundation Apache Airflow0 → 2.11.1enisa_euvdEU
apache airflow< 2.11.1nvdUScpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
Bitnami airflow< 2.11.1osvUSpkg:bitnami/airflow
PyPI apache-airflow< 2.11.1osvUSpkg:pypi/apache-airflow

advisories (4)

Vendor and ecosystem advisories describing this.

WID-SEC-W-2026-0493Apache Airflow: Mehrere SchwachstellenDeutsch2026-02-23csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um beliebigen Programmcode auszuführen oder vertrauliche Informationen offenzulegen.
GHSA-r837-hpv7-pc2fApache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table2026-02-24ghsa · osvUS
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.
BIT-airflow-2024-56373Apache Airflow: SSTI to Code Execution in Airflow through Shared DB Information2026-02-26vendor · osvUS
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.
PYSEC-2026-2355Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table2026-07-13vendor · osvUS
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.

also known as (7)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd osv cert_bund nvd NVD CVE.org MITRE

published 2026-02-24modified 2026-06-17

references (8)

External citations — patches, advisories, analysis.

http://www.openwall.com/lists/oss-security/2026/02/23/3 cnnvd
https://github.com/apache/airflow/pull/61880 cnnvd
https://lists.apache.org/thread/2vrmrhcht6g7cp5yjxpnrk2wtrncm6cy cnnvd
https://github.com/apache/airflow/pull/61880 enisa_euvd
https://lists.apache.org/thread/2vrmrhcht6g7cp5yjxpnrk2wtrncm6cy enisa_euvd
http://www.openwall.com/lists/oss-security/2026/02/23/3Mailing ListThird Party Advisorynvd
https://github.com/apache/airflow/pull/61880Issue Trackingnvd
https://lists.apache.org/thread/2vrmrhcht6g7cp5yjxpnrk2wtrncm6cyMailing ListVendor Advisorynvd

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan