Affects Apache Airflow, a widely used enterprise workflow orchestration tool; token persistence after logout can maintain access across orgs and is high-severity.
CVE-2026-86473
Airflow logout fails to revoke bearer tokens, leaving sessions valid after logout.
Is CVE-2026-86473 being exploited?
Not confirmed. CVE-2026-86473 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-86473?
CVE-2026-86473 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-86473?
Yes. A fix has been recorded for CVE-2026-86473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-86473 affect?
CVE-2026-86473 affects Apache Airflow <= 3.3.1, API clients using Authorization bearer tokens, Self-hosted and managed Airflow deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-86473?
Upgrade to apache-airflow 3.3.2+, revoke/rotate exposed tokens and audit token use
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers with a copied bearer token retain victim access until token expiry (default 24h); no extra privileges required.
Immediate action required
- affected>= 3.0.0 and < 3.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.