Categories
CVE-2026-42526 medium CVSS 5.3

Authorization Flaw in apache-airflow-providers-amazon (CVE-2026-42526)

Summary

Vulnerability in apache-airflow-providers-amazon (CVE-2026-42526). Confidential information can be exposed externally. Exploitable via conn_id. Mitigation: upgrade to 9.28.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-42526 has been found in apache-airflow-providers-amazon.
Attackers can target a specific entry point like conn_id over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade apache-airflow-providers-amazon to 9.28.0 or later.
If unsure, ask your IT team or search "apache-airflow-providers-amazon CVE-2026-42526" on the vendor's site.

CVE-2026-42526 (apache-airflow-providers-amazon) — CWE-863 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: conn_id
Patched: 9.28.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in apache-airflow-providers-amazon. Attackers reach the vulnerable code path via conn_id.

📍 Affected scope

Check the vendor advisory for the affected versions of apache-airflow-providers-amazon. Attack surface: conn_id.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 9.28.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-airflow-providers-amazon' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'apache-airflow-providers-amazon' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で apache-airflow-providers-amazon を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade apache-airflow-providers-amazon to 9.28.0

    ステージング環境で 9.28.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip apache-airflow-providers-amazon
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.28.0"}]}]
PyPI apache-airflow-providers-amazon
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.28.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details