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.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 24 Feb 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Tue, 24 Feb 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 24 Feb 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Airflow: SSTI to Code Execution in Airflow through Shared DB Information | |
| Weaknesses | CWE-94 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-02-24T15:10:20.939Z
Reserved: 2024-12-22T12:06:12.879Z
Link: CVE-2024-56373
Updated: 2026-02-24T10:18:40.546Z
Status : Undergoing Analysis
Published: 2026-02-24T10:16:02.717
Modified: 2026-02-24T16:24:05.837
Link: CVE-2024-56373
No data.
OpenCVE Enrichment
No data.