Description
Apache Airflow FAB provider: deactivating a user account does not stop tokens issued to that account before deactivation. Password authentication correctly rejects the disabled account, but the Core API continues to accept an existing, unexpired token naming it, and lets that token mint a replacement — so the account keeps its role-scoped access indefinitely after an administrator has disabled it. The user replays their own legitimate credential; no signature forgery or privilege escalation is involved, and the access stays within the roles the account already held. Affects deployments using Airflow 3 with the FAB auth manager and Core API token authentication, where an administrator deactivates an account whose row remains in the database and whose previously issued token has not expired. The trigger is administrative deactivation as a containment action, which silently fails to contain. Users of apache-airflow-providers-fab are recommended to upgrade to version 3.9.0 or later, which rejects tokens naming a deactivated account.
Affected products
apache: apache-airflow-providers-fab
References4
- github.com/apache/airflow/pull/72199 PatchVendor Advisory
- lists.apache.org/thread/85h9r50bmy8vgkgr5nyddryj1p5pxxy2 Mailing ListVendor Advisory
- lists.apache.org/thread/85h9r50bmy8vgkgr5nyddryj1p5pxxy2?users@… Mailing ListVendor Advisory
- www.openwall.com/lists/oss-security/2026/09/15/10 Mailing List
Metrics
- CVSS 3.1
-
7.2
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 63 · as of 7 November 2026
- CWE
- CWE-613
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.