Apache Airflow: Logout token revocation fails open; errors silently swallowed
Summary
| CVE | CVE-2026-113508 |
|---|---|
| State | PUBLISHED |
| Assigner | apache |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-09 10:17:05 UTC |
| Updated | 2026-11-09 11:17:20 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-613 | CWE-613 CWE-613: Insufficient Session Expiration
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Apache Software Foundation | Apache Airflow | affected 3.4.0 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/apache/airflow/pull/73788 | [email protected] | github.com | |
| github.com/apache/airflow/pull/73562 | [email protected] | github.com | |
| www.openwall.com/lists/oss-security/2026/11/09/20 | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| lists.apache.org/thread.html/6t892ozodb9f3498jrsc8k0crbdnm7no | [email protected] | lists.apache.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Claude Security Scans (en)
CNA: Pierre Jeambrun (en)
CNA: Jarek Potiuk (en)
There are currently no legacy QID mappings associated with this CVE.