The vulnerability allows an authenticated user with edit permission on one DAG to modify Task Instance state for any other DAG by exploiting a mismatch between the DAG ID in the URL path and the DAG ID in the request body. This mismatch causes the API to evaluate authorization against the wrong DAG ID, enabling unauthorized cross‑DAG mutation. The weakness is a classic Authorization Bypass (CWE‑639) that can lead to unintended data manipulation within the Airflow platform, potentially disrupting workflow executions.

Apache Airflow installations that rely on per‑DAG edit scopes, including any deployment using versions earlier than apache‑airflow 3.2.2, are affected. The official fix is available in version 3.2.2 and later.

The attack requires a legitimate Airflow account with edit permissions on at least one DAG, so the vector is likely via the authenticated UI or API. While EPSS is not published and the vulnerability is not in the CISA KEV catalog, the nature of the flaw means that an attacker with sufficient permissions could alter critical workflow state. The absence of a publicly known exploit does not negate the risk, and organizations should treat the issue as high until the patch is applied.