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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/70878 Issue Tracking, Patch
- https://lists.apache.org/thread/9nd31g40rd2zpgwwymskvjpfq1xnmllg Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · apacheNVD modified 2026-10-23 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:apache-airflow-providers-amazon:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/70878 Issue Tracking, Patch
- https://lists.apache.org/thread/9nd31g40rd2zpgwwymskvjpfq1xnmllg Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/08/10/6 Mailing List, Third Party Advisory