Apache Airflow FAB provider: FAB auth manager: JWT signature verification disabled by default for Azure AD OAuth (`verify_signature` defaults to `False`)
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.8epss 0.5%
from disclosure to weapon0 days
Published on NVDJul 29
1st PoCJul 4
exploitation probability
0.5%top 58% of all CVEs
observed exploitation
nono source reports it
2 public exploit(s)
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 (`alg:none`) ID token to the OAuth callback could bypass authentication and log in as an arbitrary user, including one holding the Admin role (CWE-347). Deployments running the FAB auth manager with the Azure AD OAuth login path under its default configuration are affected; the Authentik path already defaulted to `True`. This issue affects `apache-airflow-providers-fab` before 3.7.3. Users are advised to upgrade to `apache-airflow-providers-fab` 3.7.3, which defaults `verify_signature=True`.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Apache Software Foundation · Apache Airflow FAB providerpublic PoCs found — 2
githubgithub.com/MalHyuk/CVE-2026-59243★ 0githubgithub.com/0xdak/CVE-2026-59243_exploit★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.