Persistent API access via inactive-user token acceptance
Published Sep 16, 2026 · Updated Sep 16, 2026
Authorization bypass in Apache Airflow FAB provider 2.0.0 through 3.8.1 allows remote authenticated users to retain Core API access. FabAuthManager.deserialize_user resolves a JWT subject by user ID but fails to reject the loaded account when its active state is false. The condition requires a previously issued, unexpired token and administrative deactivation; access remains limited to the account's existing roles.
Summary
What happened
Authorization bypass in Apache Airflow FAB provider 2.0.0 through 3.8.1 allows remote authenticated users to retain Core API access. FabAuthManager.deserialize_user resolves a JWT subject by user ID but fails to reject the loaded account when its active state is false. The condition requires a previously issued, unexpired token and administrative deactivation; access remains limited to the account's existing roles.
The record
- CVE
- CVE-2026-82310
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow FAB provider
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <3.9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo