Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-75156— Apache Airflow FAB provider: FAB Azure AD OAuth: id_token issuer/audience not validated — cross-tenant authentication bypass

Quick assessment

Affected
Apache Software Foundation Apache Airflow FAB provider
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Apache Airflow FAB provider 版本 3.7.3 至 3.8.0 在通过 OAuth 登录时，未对 Azure AD 的 验证其颁发者（issuer）或受众（audience）。仅当 FAB 认证管理器配置了 Azure AD 作为 OAuth 提供方时，受影响部署才会出现此问题。由于签名密钥是从微软的多租户（multi-tenant）JWKS 端点获取的，因此由任意 Azure 租户——包括攻击者自行创建的租户——签发的 都能通过签名验证，随后用户名称和角色分配会从该攻击者控制的令牌中读取

AI Predicted 8.1 Difficulty: Moderate

Affected Version Matrix 1

VendorProduct Version RangeStatus
Apache Software Foundation Apache Airflow FAB provider 3.7.3< 3.8.1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-75156

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Apache Airflow FAB provider: FAB Azure AD OAuth: id_token issuer/audience not validated — cross-tenant authentication bypass
Source: CVE Program / CVE List V5
Vulnerability Description
Apache Airflow FAB provider versions 3.7.3 through 3.8.0 do not validate the issuer or audience of Azure AD `id_token`s 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 `id_token` 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 `id_token` 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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
源验证错误
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Apache Software Foundation Apache Airflow FAB provider 3.7.3 ~ 3.8.1 -

II. Public POCs for CVE-2026-75156

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-75156

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-75156 (1)

Mailing List Discussions for CVE-2026-75156 (1)

Vendor Pages for CVE-2026-75156 (1)

IV. Related Vulnerabilities

Same product: Apache Airflow FAB provider
Same vendor: Apache Software Foundation
Same weakness: CWE-346

V. Comments for CVE-2026-75156

No comments yet

Leave a comment