# CVE-2026-86473: Apache Airflow Core API logout incomplete token revocation

Source: https://junglewise.ai/threats/cve-2026-86473-apache-airflow-the-core-api-logout-endpoint-revokes-only-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-21. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-86473 · Severity: critical · CVSS 9.1 · Published 2026-09-21

Apache Airflow's REST API logout endpoint fails to revoke authentication tokens when clients use the documented bearer token authentication method. An attacker who has obtained a copy of a victim's token can maintain unauthorized access even after the victim has logged out, with tokens remaining valid for up to 24 hours by default. This allows persistent unauthorized API access under the victim's credentials.

Technologies: [Apache Airflow](https://junglewise.ai/threats/technologies/airflow), [apache-airflow (PyPI)](https://junglewise.ai/threats/technologies/apache-airflow). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## 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

  ```sh
  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

## References

- [https://pypi.python.org/](https://pypi.python.org/)
- [https://github.com/apache/airflow/pull/72649](https://github.com/apache/airflow/pull/72649)

## Related threats

- [Apache Airflow incomplete deserialization check bypass in scheduler](https://junglewise.ai/threats/cve-2026-96285-apache-airflow-3-3-1-shipped-a-fix-for-that-checks-the-scheduler)
- [Apache Airflow scheduler XCom deserialization privilege escalation](https://junglewise.ai/threats/cve-2026-86829-apache-airflow-s-scheduler-fully-deserializes-xcom-values-written)
- [Apache Airflow CLI audit log secrets exposure](https://junglewise.ai/threats/cve-2026-86468-apache-airflow-s-cli-records-its-arguments-in-the-audit-log-but)
- [Apache Airflow unsafe deserialization in deadline alert fields](https://junglewise.ai/threats/cve-2026-82337-apache-airflow-rebuilt-deadline-alert-fields-through-generic)
- [Apache Airflow Task SDK secret cache key collision in multi-team deployments](https://junglewise.ai/threats/cve-2026-76185-apache-airflow-s-task-sdk-secret-cache-built-its-keys-from-the)