Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 09 Nov 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache airflow |
|
| Vendors & Products |
Apache
Apache airflow |
Mon, 09 Nov 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 09 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Airflow: Logout token revocation fails open; errors silently swallowed | |
| Weaknesses | CWE-613 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-11-09T10:09:46.244Z
Reserved: 2026-10-20T10:56:16.168Z
Link: CVE-2026-113508
No data.
Status : Received
Published: 2026-11-09T10:17:05.463
Modified: 2026-11-09T11:17:20.670
Link: CVE-2026-113508
No data.
OpenCVE Enrichment
Updated: 2026-11-09T12:00:14Z
-
CWE-613
Insufficient Session Expiration