CVE-2026-75156: Apache Airflow FAB provider: FAB Azure AD OAuth: id_token issuer/audience not validated — cross-tenant authentication bypass
Apache Airflow FAB provider versions 3.7.3 through 3.8.0 do not validate the issuer or audience of Azure AD idtokens during OAuth login. Deployments are affected only when the FAB auth manager is configured with Azure AD as an OAuth provider. Because the signing keys are fetched from Microsoft's multi-tenant JWKS endpoint, an idtoken minted in any Azure tenant — including one the attacker creates — passes signature verification, and the username and role assignments are then read from that attacker-controlled token. Anyone able to register an Azure tenant can therefore authenticate to the Airflow UI with no prior access to the deployment.
The fix for CVE-2026-59243 was incomplete, and this advisory closes the remaining gap: that fix made the provider verify the idtoken signature, but did not add issuer or audience checks. Operators who already applied the CVE-2026-59243 fix are still affected and must upgrade again — 3.7.3 is the release that shipped that fix, so every version containing it falls inside this affected range. Upgrade to apache-airflow-providers-fab 3.8.1 or later.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
apache-airflow-providers-fabto a version that resolves this vulnerability.Fixed in 3.8.1Patch CVE-2026-75156 - Upgrade
Upgrade
apache-airflow-providers-fabto a version that resolves this vulnerability.Fixed in 3.7.3Patch CVE-2026-59243
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Only deployments using the FAB auth manager with Azure AD configured as an OAuth provider are affected. Versions 3.7.3 through 3.8.0 are within the affected range.
What does an attacker need to exploit it?
The attacker needs only the ability to register an Azure tenant, which allows them to obtain an id_token signed by Microsoft's multi-tenant keys. They do not need prior access to the Airflow deployment.
Does applying the earlier CVE-2026-59243 fix resolve this issue?
No. That fix added id_token signature verification but did not validate the token issuer or audience; releases containing it, starting with 3.7.3, remain affected.
What should operators do?
Upgrade apache-airflow-providers-fab to version 3.8.1 or later.