Three Apache Airflow authorization and token-handling flaws (CVE-2026-75158, CVE-2026-82355, CVE-2026-86473), all fixed in 3.3.2
Apache Airflow patches three Core API authorization flaws in version 3.3.2: an assets events endpoint that leaks events for unauthorized Dags, a session cookie that overrides an explicit bearer token, and a logout that fails to revoke bearer tokens; none are…
Three low-to-moderate severity vulnerabilities in Apache Airflow, all fixed in version 3.3.2, were announced on oss-security on 2026-09-21. CVE-2026-75158 (moderate, Airflow before 3.3.2): the /assets/events API returned asset events for every Dag, including source Dag ID, task ID, run ID, and timestamps, without a per-Dag authorization filter, so any authenticated user with asset-read access could enumerate events for Dags they were not authorized to read. CVE-2026-82355 (low, Airflow 3.3.0 before 3.3.2): when a core API request carried both a session cookie and an Authorization bearer token, Airflow authenticated the cookie principal and ignored the bearer token, reversing the intended precedence; the request executed and was audit-logged as the cookie identity, which the advisory describes as enabling session fixation. CVE-2026-86473 (low, Airflow 3.0.0 before 3.3.2): the Core API logout endpoint revoked only a session token presented as the _token cookie; a bearer credential presented in the Authorization header was not revoked despite a normal logout response, leaving a copied token valid until expiry. None of the three advisories reports exploitation in the wild.
- CVE-2026-75158 is rated moderate and affects Apache Airflow before 3.3.2.
- The /assets/events endpoint omitted a per-Dag authorization filter, exposing Dag ID, task ID, run ID, and timestamps for every Dag to any authenticated user with asset-read access.
- CVE-2026-82355 is rated low and affects Apache Airflow 3.3.0 before 3.3.2.
- A session cookie silently overrides an explicit Authorization bearer token; requests execute and are audit-logged as the cookie identity, a behavior the advisory links to session fixation.
- CVE-2026-86473 is rated low and affects Apache Airflow 3.0.0 before 3.3.2.
- Logout revokes only the _token session cookie; a bearer token remains valid until expiry even after a successful logout response.
- All three flaws are fixed in Apache Airflow 3.3.2.
- All three advisories were posted to oss-security on 2026-09-21 between 17:12 and 17:16 UTC.
Coverage timelineoldest first · each row is one article
- · 5d agoCVE-2026-75158: Apache Airflow: Assets events API returns asset events for every Dag with no per-Dag authorization filter
oss-security· 48
Apache Airflow before 3.3.2 lets asset readers enumerate events for every Dag via CVE-2026-75158.
- · 5d agoCVE-2026-82355: Apache Airflow: Session cookie silently overrides explicit Authorization bearer header, enabling session fixation
oss-security· 30
Apache Airflow lets a session cookie override a bearer token, enabling session fixation.
- · 5d ago
Vulnerabilities in this storyAll →
- CVE-2026-864739.1—Logout Fails to Revoke Bearer Tokens in Apache Airflow (CWE-613)published · Apache Airflow (apache-airflow)+2 related
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
CVE-2026-86473+2 related CVEs | Logout Fails to Revoke Bearer Tokens in Apache Airflow (CWE-613) Apache Airflow's Core API logout endpoint only revokes a session token presented via the _token cookie, so when an API client authenticates with an Authorization bearer header instead, logout returns a success response but revokes nothing. As a result, a bearer token remains valid until natural expiry, which defaults to 24 hours and is configurable. An attacker who has already obtained a copy of a victim's token keeps the victim's level of access even after the victim logs out believing the session has ended; no privileges beyond the victim's own are gained, and stealing the token in the first place is a separate problem outside this issue. Deployments whose automation or clients authenticate to the Airflow API with bearer tokens rather than the browser session cookie are affected. There is no public proof-of-concept, no known exploitation, the flaw is not in the CISA KEV catalog, and CVSS has not yet been scored. |