Skip to main content

Apache Airflow CVE-2026-75156

| EUVDEUVD-2026-72933 CRITICAL
Origin Validation Error (CWE-346)
2026-09-08 apache GHSA-vrqc-p75r-25rv
9.1
CVSS 3.1 · Vendor: apache
Share

Severity by source

Vendor (apache) PRIMARY
9.1 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI
9.1 CRITICAL

Unauthenticated remote login via a self-minted token (PR:N/AC:L) grants attacker-chosen roles giving high confidentiality and integrity over Airflow; no availability impact claimed.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

8
Metadata Corrected
Sep 08, 2026 - 19:40 vuln.today
tag: Microsoft removed
Analysis Updated
Sep 08, 2026 - 19:28 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Sep 08, 2026 - 19:23 vuln.today
cvss_changed
CVSS changed
Sep 08, 2026 - 19:23 NVD
9.1 (CRITICAL)
Metadata Corrected
Sep 08, 2026 - 17:40 vuln.today
tag: Information Disclosure replaced by Authentication Bypass
Source Code Evidence Fetched
Sep 08, 2026 - 17:28 vuln.today
Analysis Generated
Sep 08, 2026 - 17:28 vuln.today
CVE Published
Sep 08, 2026 - 16:47 cve.org
MEDIUM

DescriptionCVE.org

Apache Airflow FAB provider versions 3.7.3 through 3.8.0 do not validate the issuer or audience of Azure AD id_tokens 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.

AnalysisAI

Authentication bypass in the Apache Airflow FAB provider (apache-airflow-providers-fab 3.7.3 through 3.8.0) lets any unauthenticated attacker log into the Airflow UI when the FAB auth manager is configured with Azure AD as an OAuth provider. Because the provider validates the id_token signature against Microsoft's multi-tenant JWKS endpoint but never checks the token's issuer or audience, an id_token minted in any Azure tenant - including one the attacker registers themselves - passes verification, and the username and role assignments are then taken from that attacker-controlled token. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitable only when the Airflow FAB auth manager is configured with Azure AD as an OAuth provider (the vulnerable id_token validation path). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 9.1) is well-supported by the mechanism: a remote, unauthenticated attacker who can self-register a free Azure tenant obtains a valid-looking login with attacker-chosen username and role assignments, yielding high confidentiality and integrity impact over Airflow (DAG code, connections/secrets, and pipeline execution) with no availability impact claimed. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Vendor-released patch: upgrade apache-airflow-providers-fab to 3.8.1 or later, which adds issuer and audience validation of the Azure AD id_token (PR#71735). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: identify all Airflow instances running FAB provider versions 3.7.3 through 3.8.0 with Azure AD OAuth authentication enabled, and prioritize these as critical. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-75156 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy