top of page
perceptive_background_267k.jpg

The FAB auth manager's Azure AD OAuth login defaulted `verify_signature=False` when decoding the ID token, so an attacker able to present a forged or unsigned (…

Published:

29 juli 2026 om 00:00:00

Alert date:

29 juli 2026 om 19:02:28

Source:

nvd.nist.gov

Click to open the original link from this advisory

Identity & Access, Web Technologies, Enterprise Applications

CVE-2026-59243 affects apache-airflow-providers-fab before version 3.7.3, where the FAB auth manager's Azure AD OAuth login path defaulted to verify_signature=False when decoding JWT ID tokens. This misconfiguration allowed attackers to present forged or unsigned tokens using the alg:none algorithm to the OAuth callback endpoint, bypassing authentication entirely. An attacker could exploit this to log in as any arbitrary user, including those with Admin roles. Only deployments using the Azure AD OAuth login path under its default configuration are affected; the Authentik path was already secure. The vulnerability is classified under CWE-347 (Improper Verification of Cryptographic Signature). Users are strongly advised to upgrade to apache-airflow-providers-fab 3.7.3, which fixes the issue by defaulting verify_signature to True.

Technical details

Mitigation steps:

Affected products:

apache-airflow-providers-fab

Related links:

Related CVE's:

Related threat actors:

IOC's:

This article was created with the assistance of AI technology by Perceptive.

© 2025 by Perceptive Security. All rights reserved.

email: info@perceptivesecurity.com

Deze website toont informatie afkomstig van externe bronnen; Perceptive aanvaardt geen verantwoordelijkheid voor de juistheid, volledigheid of actualiteit van deze informatie.

bottom of page