Quick answers
- Is CVE-2026-86473 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86473 being exploited in the wild.
- How severe is CVE-2026-86473?
- Critical severity, with a CVSS score of 9.1, published 21 September 2026.
- Which products and versions are affected?
- Apache Airflow before 3.3.2; apache-airflow (PyPI) ECOSYSTEM:introduced=3.0.0,fixed=3.3.2.
- Is there a fix for CVE-2026-86473?
- Yes. apache-airflow (PyPI): upgrade to 3.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86473 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-86473?
- Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apache-airflow (PyPI): upgrade to 3.3.2 or later
pip install "apache-airflow>=3.3.2"
Technical details
The logout endpoint only revokes the _token cookie but ignores Authorization bearer headers, the documented authentication method for the Core API. An attacker with a previously obtained valid bearer token retains API access after the victim initiates logout, since the endpoint returns success without revoking the token. Fix available in version 3.3.2 and later.
Affected products
- Apache Airflow before 3.3.2
Identifiers
- CVE-2026-86473
- PYSEC-2026-3990
Timeline
- 2026-09-21: disclosed
- 2026-09-11: patched: Fix merged in PR #72649