Skip to main content
No exploitation reportedFix available

CVE-2024-56373

No exploitation reported by the sources we read.

  • Published2026-02-24
  • Fixed in2.11.1
  • WeaknessCWE-94

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-02-2410:16CVE publishedNVD

Versions per branch

NVD · OSV
Apache airflow
BranchAffectedFixed in
2.11< 2.11.12.11.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Airflowother versions: not affected

    package apache-airflowhttps://pypi.python.org

    Affected
    • < 2.11.1fixed in 2.11.1semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-24

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • airflow-2MinimOSall versions · fixed in 2.11.2-r0and 2 other packages
  • airflow-2Chainguardall versions · fixed in 2.11.1-r0and 1 other package
  • apache-airflowRoot:PyPIall versions · fixed in 2.9.3+aikido.1

Full record on NVD

Fix

  1. Update Apache airflow to 2.11.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Published
2026-02-24
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-r837-hpv7-pc2f

Frequently asked questions

What is CVE-2024-56373?

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.

Is CVE-2024-56373 actively exploited?

Active exploitation of CVE-2024-56373 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-56373?

CVE-2024-56373 has a CVSS v3 base score of 8.4 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H.

Running airflow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record