CVE-2026-41084: CWE-639: Authorization Bypass Through User-Controlled Key in Apache Software Foundation Apache Airflow
A bug in Apache Airflow's bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag's ID in the URL path and naming the target Dag's IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
AI Analysis
Technical Summary
Apache Airflow 3.2.0 contains an authorization bypass vulnerability (CWE-639) in its bulk Task Instances API endpoints (PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances). The API evaluates authorization against the dag_id from the URL path but operates on dag_id and dag_run_id values extracted from the request body. This mismatch allows an authenticated user with edit permission on one DAG to alter task instance states in other DAGs by specifying those DAGs in the request body while keeping the authorized DAG's ID in the URL path. This flaw undermines per-DAG edit-scope isolation controls. The vendor recommends upgrading to Apache Airflow 3.2.2 or later to fix this issue.
Potential Impact
An authenticated user with edit permissions on a single DAG can bypass intended authorization boundaries and modify task instance states in other DAGs. This could lead to unauthorized changes in workflow execution states across DAGs, potentially disrupting operations or causing data integrity issues in multi-tenant or team-isolated environments. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.2.2 or later, where this authorization bypass vulnerability has been addressed. No other mitigation or temporary workaround is specified. Patch status is not explicitly confirmed in the vendor advisory, but the recommendation to upgrade indicates an official fix is available in 3.2.2.
CVE-2026-41084: CWE-639: Authorization Bypass Through User-Controlled Key in Apache Software Foundation Apache Airflow
Description
A bug in Apache Airflow's bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag's ID in the URL path and naming the target Dag's IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Airflow 3.2.0 contains an authorization bypass vulnerability (CWE-639) in its bulk Task Instances API endpoints (PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances). The API evaluates authorization against the dag_id from the URL path but operates on dag_id and dag_run_id values extracted from the request body. This mismatch allows an authenticated user with edit permission on one DAG to alter task instance states in other DAGs by specifying those DAGs in the request body while keeping the authorized DAG's ID in the URL path. This flaw undermines per-DAG edit-scope isolation controls. The vendor recommends upgrading to Apache Airflow 3.2.2 or later to fix this issue.
Potential Impact
An authenticated user with edit permissions on a single DAG can bypass intended authorization boundaries and modify task instance states in other DAGs. This could lead to unauthorized changes in workflow execution states across DAGs, potentially disrupting operations or causing data integrity issues in multi-tenant or team-isolated environments. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.2.2 or later, where this authorization bypass vulnerability has been addressed. No other mitigation or temporary workaround is specified. Patch status is not explicitly confirmed in the vendor advisory, but the recommendation to upgrade indicates an official fix is available in 3.2.2.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-04-16T18:11:57.535Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e71e29bf47b50cd4973
Added to database: 6/1/2026, 9:18:41 AM
Last enriched: 6/1/2026, 9:48:35 AM
Last updated: 6/2/2026, 5:06:12 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.