You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
In the AWS Secrets Manager and SSM Parameter Store secrets backends of `apache-airflow-providers-amazon` prior to 9.28.0, the team-scoping logic could resolve a `conn_id` containing a `/` (e.g. `"my_team/conn"`) to the same path as another team's team-scoped secret when the caller had no team context. A privileged caller without team context could therefore retrieve another team's secret by crafting a colliding `conn_id`. Fixed in 9.28.0 by switching the team-scope separator to `--` and rejecting team-shaped `conn_id`s when team context is absent. Affects the experimental multi-tenant teams feature only. Users are recommended to upgrade to `apache-airflow-providers-amazon` 9.28.0, which fixes the issue.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: Apache Airflow Amazon provider, Description: En los backends de secretos de AWS Secrets Manager y SSM Parameter Store de 'apache-airflow-providers-amazon' anteriores a la versión 9.28.0, la lógica de alcance de equipo podría resolver un 'conn_id' que contuviera un / (por ejemplo, my_team/conn ) a la misma ruta que un secreto con alcance de equipo de otro equipo cuando el llamador no tenía contexto de equipo. Un llamador privilegiado sin contexto de equipo podría, por lo tanto, recuperar el secreto de otro equipo al crear un 'conn_id' en colisión. Corregido en la versión 9.28.0 al cambiar el separador de alcance de equipo a -- y rechazando los 'conn_id' con forma de equipo cuando el contexto de equipo está ausente. Afecta solo a la característica experimental de equipos multi-inquilino. Se recomienda a los usuarios actualizar a 'apache-airflow-providers-amazon' 9.28.0, que corrige el problema.
Reanalysis by NIST7/02/2026 12:36:03 PM
Action
Type
Old Value
New Value
Changed
CPE Configuration
OR
*cpe:2.3:a:apache:airflow_providers_amazon:*:*:*:*:*:*:*:* versions up to (excluding) 9.28.0
OR
*cpe:2.3:a:apache:apache-airflow-providers-amazon:*:*:*:*:*:*:*:* versions up to (excluding) 9.28.0
Initial Analysis by NIST6/30/2026 12:17:40 PM
Action
Type
Old Value
New Value
Added
CPE Configuration
OR
*cpe:2.3:a:apache:airflow_providers_amazon:*:*:*:*:*:*:*:* versions up to (excluding) 9.28.0
New CVE Received from Apache Software Foundation5/19/2026 4:16:19 PM
Action
Type
Old Value
New Value
Added
Description
In the AWS Secrets Manager and SSM Parameter Store secrets backends of `apache-airflow-providers-amazon` prior to 9.28.0, the team-scoping logic could resolve a `conn_id` containing a `/` (e.g. `"my_team/conn"`) to the same path as another team's team-scoped secret when the caller had no team context. A privileged caller without team context could therefore retrieve another team's secret by crafting a colliding `conn_id`. Fixed in 9.28.0 by switching the team-scope separator to `--` and rejecting team-shaped `conn_id`s when team context is absent. Affects the experimental multi-tenant teams feature only. Users are recommended to upgrade to `apache-airflow-providers-amazon` 9.28.0, which fixes the issue.