CVE-2026-113508
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…
Auswirkung
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.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Bei Erfolg: hohes Risiko, dass Daten ausgelesen werden.
Betroffene Produkte · Apache Software Foundation
| Produkt | Betroffene Versionen |
|---|---|
| Apache Airflow | vor 3.4.0 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- 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
- https://github.com/advisories/GHSA-fc7p-hr7f-vwgr
- https://nvd.nist.gov/vuln/detail/CVE-2026-113508