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