Operation on a Resource after Expiration or Release Affecting apache-airflow-core package, versions [,3.4.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-APACHEAIRFLOWCORE-22391927
- published10 Nov 2026
- disclosed9 Nov 2026
- creditUnknown
Introduced: 9 Nov 2026
NewCVE-2026-113508 (opens in a new tab)How to fix?
Upgrade apache-airflow-core to version 3.4.0 or higher.
Overview
Affected versions of this package are vulnerable to Operation on a Resource after Expiration or Release via the logout endpoint, which silently swallows any error that occurs during server-side token revocation and reports success regardless. When an auth manager (such as FAB or Keycloak) redirects logout to an external URL, server-side revocation is the only mechanism that invalidates the Airflow token. Revocation fails on database errors and, reliably, for tokens issued by an external identity provider accepted via [api_auth] trusted_jwks_url whose jti claim exceeds 32 characters - overflowing the revoked_token.jti column and raising a DataError on PostgreSQL and MySQL. An attacker who obtains a copy of a user's token before logout can continue using it against the Airflow API until the token naturally expires.