PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75156 Apache Software Foundation CVE debrief

CVE-2026-75156 debrief: Apache Airflow FAB provider vulnerable to unauthorized authentication via Azure AD OAuth. The vulnerability allows attackers to authenticate to Airflow UI with no prior access by registering an Azure tenant and minting an id_token. Affected deployments are those with Azure AD configured as an OAuth provider. The fix involves upgrading to apache-airflow-providers-fab 3.8.1 or later. This issue is related to incomplete fixes for CVE-2026-59243, which did not include issuer or audience checks for Azure AD id_tokens.

Vendor
Apache Software Foundation
Product
Apache Airflow FAB provider
CVSS
CRITICAL 9.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-08
Original CVE updated
2026-09-16
Advisory published
2026-09-08
Advisory updated
2026-09-16

Who should care

Airflow administrators and users who have Azure AD configured as an OAuth provider should assess exposure and upgrade to a fixed version. This includes reviewing current configurations, verifying authentication mechanisms, and ensuring that all necessary security measures are in place to prevent unauthorized access.

Why it matters

CVE-2026-75156 allows attackers to authenticate to Airflow UI via Azure AD OAuth without prior access. Airflow administrators and users with Azure AD OAuth configured should verify exposure and upgrade to apache-airflow-providers-fab 3.8.1 or later.

  • Potential unauthorized authentication to Airflow UI
  • Possible elevation of privileges for attackers
  • Need for verification of authentication and authorization mechanisms
  • Priority on upgrading to a fixed version

Technical summary

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. This allows an attacker to authenticate to the Airflow UI with no prior access to the deployment by registering an Azure tenant and minting an id_token. The fix involves upgrading to apache-airflow-providers-fab 3.8.1 or later, which includes the necessary validation checks. Operators who already applied the CVE-2026-59243 fix are still affected and must upgrade again. The CVE record and NVD entry provide details on the vulnerability.

Defensive priority

High

Recommended defensive actions

  • Upgrade to apache-airflow-providers-fab 3.8.1 or later
  • Review and update Azure AD OAuth provider configurations
  • Verify authentication and authorization mechanisms
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Apache Airflow FAB provider versions 3.7.3 through 3.8.0. The issue is related to the lack of validation of the issuer or audience of Azure AD id_tokens during OAuth login.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75156 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75156

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75156 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75156

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.