Categories
CVE-2026-32228

Authorization Flaw in apache-airflow-core (CVE-2026-32228)

Summary

Vulnerability in apache-airflow-core (CVE-2026-32228). Confidential information can be exposed externally. Mitigation: upgrade to 3.2.0 or later.

Original description

The description as published by the source.

UI / API User with asset materialize permission could trigger dags they had no access to. Users are advised to migrate to Airflow version 3.2.0 that fixes the issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-32228 has been found in apache-airflow-core.
Confidential information can be exposed externally.
What to do: upgrade apache-airflow-core to 3.2.0 or later.
If unsure, ask your IT team or search "apache-airflow-core CVE-2026-32228" on the vendor's site.

CVE-2026-32228 (apache-airflow-core) — CWE-863
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.2.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-core.

📍 Affected scope

Check the vendor advisory for the affected versions of apache-airflow-core.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 3.2.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-core' . 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-core' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade apache-airflow-core to 3.2.0

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

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

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

Affected packages

PyPI apache-airflow-core
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.2.0"}]}]

References

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