# CVE-2026-113508: Apache Airflow logout token revocation failure

Source: https://junglewise.ai/threats/cve-2026-113508-apache-airflow-s-logout-endpoint-attempted-to-revoke-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-113508 · Severity: info · Published 2026-11-09

Apache Airflow is a workflow orchestration platform that manages data pipelines and job scheduling. When users log out, the system is supposed to revoke their authentication tokens on the server, but failures during revocation were silently ignored and logout still reported success. An attacker who obtained a user's token before logout could continue using it against the Airflow API until it naturally expired, potentially gaining unauthorized access to sensitive workflows and data.

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

## Quick answers

**Is CVE-2026-113508 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-113508 being exploited in the wild.

**How severe is CVE-2026-113508?** Informational severity, published 9 November 2026.

**Which products and versions are affected?** Apache Airflow before 3.4.0.

**Is there a fix for CVE-2026-113508?** Yes: fixed in Apache Airflow 3.4.0 and later. Until then: Restrict API access to trusted networks or implement additional authentication layers independent of token revocation, such as IP whitelisting or requiring re-authentication for sensitive operations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-113508 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-113508?** Check whether you run Apache Airflow 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

- Fixed in Apache Airflow 3.4.0 and later

Restrict API access to trusted networks or implement additional authentication layers independent of token revocation, such as IP whitelisting or requiring re-authentication for sensitive operations.

## Technical details

The vulnerability is a silent failure in the logout endpoint's token revocation mechanism. When external auth managers (FAB, Keycloak) or external JWT issuers are used, server-side token revocation is the primary invalidation mechanism. The revocation fails on database errors and for external JWT tokens with identifiers longer than 32 characters (which overflow the revoked_token.jti column), yet logout returns success without reporting the failure, leaving tokens valid in the API.

## Affected products

- Apache Airflow before 3.4.0

## Timeline

- 2026-11-09: disclosed

## References

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

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