CVE-2026-75157

Apache Airflow: Asset queued-events DELETE endpoints gated on Dag READ instead of Dag EDIT (asset-triggered scheduling suppression)

Published Sep 18, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Apache Airflow's asset queued-events DELETE endpoints checked the caller's Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag's queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.

Analysis

AI-generated

Technical impact

Apache Airflow’s asset queued‑events DELETE endpoints incorrectly check the caller’s Dag‑axis permission, allowing any authenticated user who possesses read access to a Dag to delete the Dag’s queued asset events. This state‑changing action silently suppresses asset‑triggered scheduling for that Dag, enabling a malicious actor to interrupt or block scheduled runs by manipulating queued events. The weakness is a read‑to‑write privilege escalation (CWE‑863).

Affected Systems

The vulnerability affects Apache Airflow deployments that use asset‑triggered scheduling and grant Dag read access to users who do not have Dag edit rights. All versions prior to 3.3.2 are susceptible; upgrading to apache‑airflow 3.3.2 or later removes the flaw.

Risk and Exploitability

The flaw requires only authentication and a standard read permission, so an internal or compromised account can perform the attack. With a CVSS score of 7.5, the vulnerability is considered high severity; however, because the EPSS score is below 1% and the issue is not yet listed in CISA’s KEV catalog, exploitation likelihood remains low at present. Nevertheless, the impact on workflow availability is high, and the lack of proper authorization checks raises the overall risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Airflow to 3.3.2 or later, which corrects the permission check for queued‑event deletion.
  • Restrict Dag READ permissions so that only users who also have Dag EDIT privileges can access them.
  • Monitor and log asset queued‑event deletions, and set alerts for anomalous activity.

Generated by OpenCVE AI on September 22, 2026 at 20:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache airflow
Vendors & Products Apache
Apache airflow
Type Values Removed Values Added
Description Apache Airflow's asset queued-events DELETE endpoints checked the caller's Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag's queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.
Title Apache Airflow: Asset queued-events DELETE endpoints gated on Dag READ instead of Dag EDIT (asset-triggered scheduling suppression)
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 3, 2026, 7:00 AM
Reserved
Aug 17, 2026, 6:58 PM
Status
Awaiting Analysis
Published
Sep 18, 2026, 8:17 AM
Modified
Nov 3, 2026, 7:20 AM