原文の説明
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.
影響を受けるソフトウェア
- Apache Airflow * リポジトリ・パッケージ一致
詳細
- 公開日
- 2026-09-09
- 最終更新
- 2026-09-16
- CVSS ベクター
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N- CWE
- CWE-346
- EPSS(30日以内の悪用確率)
- 0.38% (パーセンタイル 32)
参考資料
本製品は NVD API のデータを使用していますが、NVD による承認または認定を受けたものではありません。CVE® は The MITRE Corporation の登録商標です。CVE レコードは CVE Program の利用規約に基づいて使用しています。