Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-75156 – Authentication Bypass – Apache Airflow FAB Provider 3.7.3–3.8.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75156 is an authentication bypass vulnerability (CWE-346, Origin Validation Error) in the Apache Airflow FAB provider’s Azure AD OAuth integration. The provider fails to validate the issuer and audience claims of Azure AD id_tokens, allowing an attacker who registers their own Azure tenant to forge a token that is accepted by the target Airflow deployment. The vulnerability carries a CVSS v3.1 base score of 9.1 (Critical) and represents an incomplete fix for the earlier CVE-2026-59243.

Technical details

  • Root cause: the FAB provider verifies the signature of an Azure AD id_token but does not validate its issuer (iss) or audience (aud) claims.
  • Because 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.
  • Trigger condition: the deployment must have the FAB auth manager configured to use Azure AD as its OAuth provider.
  • Attack vector: network, no privileges and no user interaction required (AC:L, PR:N, UI:N).
  • Impact: an attacker can authenticate to the Airflow web UI without any prior access to the deployment, with the username and role assignments read directly from the attacker-controlled token, leading to full confidentiality and integrity impact.
  • This is a follow-up to CVE-2026-59243: that earlier fix added signature verification but did not add issuer/audience checks, so deployments patched only for CVE-2026-59243 remain exposed.

Affected software

  • Apache Airflow FAB provider (apache-airflow-providers-fab) versions 3.7.3 through 3.8.0, when configured with Azure AD as the OAuth provider.

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: upgrade apache-airflow-providers-fab to version 3.8.1 or later.
  • If patching is not immediately possible: disable or restrict Azure AD OAuth login for the FAB auth manager, or restrict network access to the Airflow web UI until the upgrade can be applied.
  • Do not rely solely on having applied the CVE-2026-59243 fix — it does not close this authentication bypass.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Sign In - Airflow

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge