Skip to content
VulniPulse
Medium 1 vendor · 3 advisories

CVE-2026-68872: Apache Airflow Amazon provider: amazon SSM / Secrets Manager backends: team-scope guard bypass resolves another team's Connection or Variable

CVE-2026-68872 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.5 (Apache)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N · base score 6.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-639: Authorization Bypass Through User-Controlled Key
EPSS
0.60% chance of exploitation in the next 30 days (49th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Apache: 9.34.0
Vendor advisories
3 from Apache
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-68872; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

The AWS Systems Manager Parameter Store and Secrets Manager backends in Apache Airflow's Amazon 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 either 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 one of these backends. Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.

Text from the CVE.org record (apache).

How do I fix CVE-2026-68872?

Upgrade to a fixed release named by the vendor:

  • Apache: 9.34.0
  • Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace. (Apache)

Vendor advisories for CVE-2026-68872

Apache

3 advisories
  • Advisory severityMedium6.5

    Medium [CVE-2026-68870 +4] Apache Airflow HashiCorp provider: the HashiCorp Vault secrets backend's team-scope guard can be bypassed with a user-controlled key

    CVE-2026-97636Source published Source updated

    This bulletin covers 5 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Apache Airflow HashiCorp provider: the HashiCorp Vault secrets backend's team-scope guard can be bypassed with a user-controlled key. In a multi-team deployment, a Dag author scoped to one team can supply a Variable key containing a path separator that causes the backend to resolve a secret belonging to a different team, because after the team-scoped lookup misses the backend falls back to a team-agnostic path concatenated from the unvalidated key. The Execution API Variables route accepts a path-shaped key, so this is reachable from ordinary Dag code. Affects multi-team deployments using the HashiCorp Vault secrets backend. Single-team deployments are not affected, as there is no cross-team boundary to cross. This is the same class as CVE-2026-86465, CVE-2026-68870, CVE-2026-68871 and…

    Related products — impact not confirmed
    • Apache Airflow HashiCorp
    Source-reported affected versions
    • Apache Airflow HashiCorp provider 4.6.0 before 4.8.0
    Source-reported fixed versions
    • 4.8.0
    Mitigation guidance
    • Users of apache-airflow-providers-hashicorp are recommended to upgrade to version 4.8.0 or later, which fixes the issue.
  • Advisory severityMedium6.5

    Medium [CVE-2026-68870 +3] Apache Airflow Akeyless provider: the Akeyless secrets backend's team-scope guard can be bypassed with a user-controlled key

    CVE-2026-86465Source published Source updated

    This bulletin covers 4 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Apache Airflow Akeyless provider: the Akeyless secrets backend's team-scope guard can be bypassed with a user-controlled key. In a multi-team deployment, a Dag author scoped to one team can supply a Variable key containing a path separator that causes the backend to resolve a secret belonging to a different team, because the lookup path is concatenated from an unvalidated key after the team-scoped lookup misses. The Execution API Variables route accepts a path-shaped key, so this is reachable from ordinary Dag code. Affects multi-team deployments using the Akeyless secrets backend. Single-team deployments are not affected, as there is no cross-team boundary to cross. This is the same class as CVE-2026-68870, CVE-2026-68871 and CVE-2026-68872 in the Azure Key Vault, Yandex Lockbox and…

    Related products — impact not confirmed
    • Apache Airflow Akeyless
    Source-reported affected versions
    • Apache Airflow Akeyless provider before 0.3.1
    Source-reported fixed versions
    • 0.3.1
    Mitigation guidance
    • Users of apache-airflow-providers-akeyless are recommended to upgrade to version 0.3.1 or later, which fixes the issue.
  • Advisory severityMedium6.5

    Medium [CVE-2026-68872] Apache Airflow Amazon provider: amazon SSM / Secrets Manager backends: team-scope guard bypass resolves another team's Connection or Variable

    CVE-2026-68872Source published Source updated

    The AWS Systems Manager Parameter Store and Secrets Manager backends in Apache Airflow's Amazon 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 either 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 one of these backends. Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace. Affected product named by the advisory: Apache Airflow Amazon provider.

    Affected products in this advisory
    • Apache Airflow
    Source-reported affected versions
    • Apache Airflow Amazon provider before 9.34.0
    Source-reported fixed versions
    • 9.34.0
    Mitigation guidance
    • Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache