CVE-2026-42526

MEDIUMNVD 5.35.3—

5.3

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_ids 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.

CVSS v3: 5.3
EG Score: 5.3(high)
EPSS: 7.9%
KEV: Not listed

Published

May 19, 2026

Last Modified

May 19, 2026

References (3)

security@apachehttps://github.com/apache/airflow/pull/65703
security@apachehttps://lists.apache.org/thread/0092sz5g520d3qqjb01wd61myqlgjtyn
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2026/05/19/36

Vendor Advisories for CVE-2026-42526(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

GHSA-g9qc-qf28-hhqx
GitHub Security AdvisoriesMedium
In the AWS Secrets Manager and SSM Parameter Store secrets backends of `apache-airflow-providers...

Frequently asked(5)

What is CVE-2026-42526?

CVE-2026-42526 is a medium vulnerability published on May 19, 2026. 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 connid containing a / (e.g. "myteam/conn") to the same path as another team's team-scoped secret when the caller had no team context. A…

When was CVE-2026-42526 disclosed?

CVE-2026-42526 was first published in the National Vulnerability Database on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-42526 actively exploited?

CVE-2026-42526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-42526?

CVE-2026-42526 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2026-42526?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42526, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42526

Explore →

Is Your Infrastructure Affected by CVE-2026-42526?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-42526

📅 Published

🔄 Last Modified

🔗 References (3)

📣 Vendor Advisories for CVE-2026-42526(1)

❓ Frequently asked(5)