CVE-2026-82310: Apache Airflow FAB provider: deactivating a user account does not stop tokens issued to that account before deactivation
This Apache advisory covers CVE-2026-82310. Related products: Apache Airflow FAB.
- CVE-2026-82310
Key facts
- Vendor rating
- High, CVSS 7.2
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H· base score 7.2, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: high. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.- Weakness
- CWE-613: Insufficient Session Expiration
- EPSS
- 1.00% chance of exploitation in the next 30 days (63rd percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Versions named
- Apache Airflow FAB provider 2.0.0 before 3.9.0
- Fixed in
- 3.9.0
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
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.
Text from the source record.
- Apache Airflow FAB provider 2.0.0 before 3.9.0
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-82310
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users of apache-airflow-providers-fab are recommended to upgrade to version 3.9.0 or later, which rejects tokens naming a deactivated account.
End-of-life dates for Apache Airflow
More Apache Software Foundation advisories
CVE-2026-86466Sep 16, 2026Apache Airflow FAB provider: the Authentik OAuth path in the FAB auth managerCVE-2026-86462Sep 16, 2026Apache Airflow FAB provider: changing a user's password through the Admin user-edit PATCHCVE-2026-82311Sep 16, 2026Apache Airflow FAB provider: resetting a user's password does not deleteCVE-2026-75156Sep 8, 2026Apache Airflow FAB provider: FAB Azure AD OAuth: id_token issuer/audience not validatedCVE-2026-59245Jul 13, 2026Apache Airflow FAB provider: FAB auth manager: a DAG named "DAGs" hijacks the globalCVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writing
Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories
Get an email when Apache Airflow publishes the next one.
See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.