Scheduling suppression via read-gated queued-event deletion
Published Sep 18, 2026 · Updated Sep 18, 2026
Incorrect authorization in Apache Airflow before 3.3.2 allows remote authenticated users to suppress asset-triggered Dag scheduling. The three queued-events DELETE endpoints authorize the Dag axis with READ while deleting AssetDagRunQueue rows instead of requiring EDIT. Exploitation requires global Assets delete plus Dag read permission and removes pending events without granting Dag edit access.
Summary
What happened
Incorrect authorization in Apache Airflow before 3.3.2 allows remote authenticated users to suppress asset-triggered Dag scheduling. The three queued-events DELETE endpoints authorize the Dag axis with READ while deleting AssetDagRunQueue rows instead of requiring EDIT. Exploitation requires global Assets delete plus Dag read permission and removes pending events without granting Dag edit access.
The record
- CVE
- CVE-2026-75157
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started