Homepage

Arbitrary Code Injection Affecting airflow-2-compat package, versions <2.11.2-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-AIRFLOW2COMPAT-15675025
  • published18 Mar 2026
  • disclosed24 Feb 2026
Report a new vulnerability Found a mistake?

Introduced: 24 Feb 2026

NewCVE-2024-56373  (opens in a new tab)
CWE-94  (opens in a new tab)

How to fix?

Upgrade Minimos:latest airflow-2-compat to version 2.11.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream airflow-2-compat package and not the airflow-2-compat package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.