CVE-2026-46764: CWE-639: Authorization Bypass Through User-Controlled Key in Apache Software Foundation Apache Airflow
The Event Log detail endpoint `GET /api/v2/eventLogs/{event_log_id}` in Apache Airflow fetched audit-log rows directly by numeric ID after only the generic Audit Log permission check, while the collection endpoint `GET /api/v2/eventLogs` applied per-Dag scoping. An authenticated UI/API user with audit-log read permission for one Dag could retrieve audit-log entries for any other Dag by guessing or enumerating the numeric event log ID. Affects deployments that rely on per-Dag audit-log scoping. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
AI Analysis
Technical Summary
The vulnerability in Apache Airflow's API v2 Event Log detail endpoint allows an authenticated user with audit-log read permission for a specific Dag to retrieve audit-log entries for other Dags by enumerating numeric event log IDs. This is due to the endpoint fetching audit-log rows by numeric ID after only a generic Audit Log permission check, lacking the per-Dag scoping applied in the collection endpoint. This authorization bypass (CWE-639) can lead to unauthorized access to audit logs across Dags within the same Airflow deployment. The issue affects versions prior to 3.2.2, which includes the fix.
Potential Impact
An authenticated user with audit-log read permission scoped to a single Dag can access audit-log entries for other Dags, potentially exposing sensitive audit information beyond their authorized scope. This could lead to unauthorized disclosure of audit logs within the Airflow environment. There are no 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 fixed. No other mitigations are indicated. Patch status is confirmed by the vendor advisory recommending upgrade to 3.2.2+.
CVE-2026-46764: CWE-639: Authorization Bypass Through User-Controlled Key in Apache Software Foundation Apache Airflow
Description
The Event Log detail endpoint `GET /api/v2/eventLogs/{event_log_id}` in Apache Airflow fetched audit-log rows directly by numeric ID after only the generic Audit Log permission check, while the collection endpoint `GET /api/v2/eventLogs` applied per-Dag scoping. An authenticated UI/API user with audit-log read permission for one Dag could retrieve audit-log entries for any other Dag by guessing or enumerating the numeric event log ID. Affects deployments that rely on per-Dag audit-log scoping. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Apache Airflow's API v2 Event Log detail endpoint allows an authenticated user with audit-log read permission for a specific Dag to retrieve audit-log entries for other Dags by enumerating numeric event log IDs. This is due to the endpoint fetching audit-log rows by numeric ID after only a generic Audit Log permission check, lacking the per-Dag scoping applied in the collection endpoint. This authorization bypass (CWE-639) can lead to unauthorized access to audit logs across Dags within the same Airflow deployment. The issue affects versions prior to 3.2.2, which includes the fix.
Potential Impact
An authenticated user with audit-log read permission scoped to a single Dag can access audit-log entries for other Dags, potentially exposing sensitive audit information beyond their authorized scope. This could lead to unauthorized disclosure of audit logs within the Airflow environment. There are no 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 fixed. No other mitigations are indicated. Patch status is confirmed by the vendor advisory recommending upgrade to 3.2.2+.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-18T15:42:29.004Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e75e29bf47b50cd4a16
Added to database: 6/1/2026, 9:18:45 AM
Last enriched: 6/1/2026, 9:35:17 AM
Last updated: 6/2/2026, 7:10:20 AM
Views: 13
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.