Answer in brief
CVE-2026-75158 records a Medium severity (CVSS 4.3) vulnerability in Apache Airflow: Assets events API returns asset events for every Dag with no per-Dag authorization filter. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/Apache Airflow (generic), Apache Software Foundation/apache-airflow-core (generic), apache-airflow (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/apache-airflow (generic), Apache Software Foundation/Apache Airflow (generic), Apache Software Foundation/apache-airflow-core (generic), apache-airflow (pypi). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/apache-airflowgeneric | >=0 <3.0.0 | 3.0.0 |
| Apache Software Foundation/Apache Airflowgeneric | >=0 <3.3.2 | 3.3.2 |
| Apache Software Foundation/apache-airflow-coregeneric | >=3.0.0 <3.3.2 | 3.3.2 |
| apache-airflowpypi | >=0 <3.3.2 | 3.3.2 |
Published upstream
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 21, 2026
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. Because the filter was also absent from the count query, `total_entries` and pagination disclosed the existence of hidden Dags even without inspecting individual rows. Deployments are affected whenever per-Dag access control is used to separate teams or tenants; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.
Quoted source text, attributed separately from HOL analysis.