CVE-2026-75158 Apache Software Foundation CVE debrief

Who should care

Airflow administrators and security teams should assess exposure and take action to prevent unauthorized access to asset events. They should review and adjust access controls for asset-read access, monitor for unauthorized access to asset events, and consider implementing compensating controls for exposed systems.

Why it matters

CVE-2026-75158 allows authenticated users with asset-read access to enumerate asset events for Dags they are not authorized to see, potentially leading to unauthorized access or reconnaissance.

• Enumeration of asset events for unauthorized Dags
• Disclosure of source Dag ID, task ID, run ID, and event timestamps
• Potential for lateral movement or reconnaissance
• Verification of access controls and asset event permissions

Technical summary

Apache Airflow's `/assets/events` API returned asset events for every Dag in the deployment, with no filter restricting them to the Dags the caller is authorized to read. Any authenticated user holding asset-read access could therefore enumerate asset events — including the source Dag ID, task ID, run ID and event timestamps — for Dags they have no permission to see. The vulnerability affects deployments using per-Dag access control to separate teams or tenants, with no special configuration required. The issue was addressed in apache-airflow 3.3.2.

Defensive priority

Airflow administrators and security teams should assess exposure and upgrade to version 3.3.2 or later.

Recommended defensive actions

• Upgrade to apache-airflow 3.3.2 or later
• Review and adjust access controls for asset-read access
• Monitor for unauthorized access to asset events
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. The NVD entry is currently Analyzed. The vulnerability was disclosed by the Apache Airflow team, and the CVE was assigned by the CVE Program. The NVD entry provides additional information on the vulnerability, including its CVSS score and severity. The CVE record and NVD entry are the primary sources of information for this vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.