CVE-2026-68870

Apache Airflow Microsoft Azure provider: microsoft.azure Key Vault backend: team-scope guard bypass resolves another team's Connection or Variable

Published Aug 10, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 14.1.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.

Analysis

AI-generated

Technical impact

The Azure Key Vault backend in Apache Airflow’s Microsoft Azure provider falls back to a team‑agnostic lookup when a team‑scoped Connection or Variable lookup fails. This logic allows a lookup request that specifies another team’s namespace to be resolved, thereby returning that team’s secret. The flaw is an authorization bypass (CWE‑639) that leads to disclosure of sensitive credentials.

Affected Systems

Apache Airflow’s Microsoft Azure provider, specifically deployments running multi‑team mode with the Azure Key Vault secrets backend and using provider versions before 14.1.0.

Risk and Exploitability

Any user who can invoke the Airflow backend in a multi‑team environment—such as a developer or administrator with normal team access—can supply an identifier that spells another team’s namespace and trigger the fallback. No additional privileges are required. The vulnerability enables full credential disclosure. EPSS score is < 1%, the issue is not listed in CISA KEV, and CVSS score is 5.3, but the impact of bypassing team isolation is severe, making the risk high for environments that store sensitive secrets.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to apache-airflow-providers-microsoft-azure version 14.1.0 or later, which rejects team‑agnostic fall‑through for identifiers that could name a team namespace.
  • If an upgrade cannot be applied immediately, disable Airflow’s multi‑team mode or restrict usage of the Azure Key Vault backend to trusted teams only.
  • Audit existing secrets for unintended cross‑team exposure and rotate credentials that could have been compromised.

Generated by OpenCVE AI on August 13, 2026 at 03:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache airflow Microsoft Azure Provider
Vendors & Products Apache
Apache airflow Microsoft Azure Provider
Type Values Removed Values Added
Description The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 14.1.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.
Title Apache Airflow Microsoft Azure provider: microsoft.azure Key Vault backend: team-scope guard bypass resolves another team's Connection or Variable
Weaknesses CWE-639
References
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 16, 2026, 2:56 PM
Reserved
Jul 31, 2026, 7:39 PM
Status
Awaiting Analysis
Published
Aug 10, 2026, 7:17 PM
Modified
Oct 24, 2026, 4:10 PM