CyberRota Analysis
AI-GeneratedApache Airflow's FAB auth manager is vulnerable due to inadequate validation of issuer and audience claims in the Authentik OAuth token, allowing attackers with valid tokens from other applications to authenticate as any user. This flaw primarily affects deployments using the FAB auth manager with Authentik OAuth, especially those serving multiple applications from the same Authentik instance. Organizations utilizing Apache Airflow with this configuration should prioritize upgrading to version 3.9.0 or later to mitigate the risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Apache Airflow FAB provider: the Authentik OAuth path in the FAB auth manager does not validate the issuer or audience claims of the id_token it accepts. An attacker holding a token that the same Authentik identity provider minted for a different client application can present it to Airflow and be authenticated as the user it names, because the audience claim is never checked. Affects deployments using the FAB auth manager with Authentik OAuth where the same Authentik instance also serves other applications; the attacker needs a valid token for any of those other applications, not for Airflow. CVE-2026-75156 corrected the same missing validation on the Azure AD path in this file; the Authentik path was left unchanged and is fixed here. Deployments that applied the CVE-2026-75156 fix and use Authentik must also upgrade for this one. Users of apache-airflow-providers-fab are recommended to upgrade to version 3.9.0 or later, which fixes the issue.
Related CVEs
Other vulnerabilities affecting the same vendor(s)