CVE-2026-59243CWE-347

CVE-2026-59243

Critical · published July 29, 2026

CVSS v3.1
9.8
EPSS
1%
Percentile
50.2
In the wild
Unconfirmed
What it is

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`.

The record
Technical detail
CVSS v3.1
9.8 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00643 · 50.2th percentile
Weakness
CWE-347 · Improper Verification of Cryptographic Signature
Published
2026-07-29T14:16Z
Affected products (1)
ProductVersionsFixed in
apache/apache-airflow-providers-fab< 3.7.33.7.3
References (3)
EPSS history
Timeline
  • 29 JUL 08:35Z
    Apache Airflow FAB provider: FAB auth manager: JWT signature verification disabled by default for Azure AD OAuth (`verify_signature` defaults to `False`)
    cvelistv5