HighGHSA-h97w-pm3w-mwmcBIT-airflow-2026-32228CVE-2026-32228PYSEC-2026-2360

Apache Airflow allows users with asset materialize permissions to trigger DAGs outside of their permissions

Published 18 Apr 2026 · Updated 13 Jul 2026

Is your project on an affected apache-airflow-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=3.0.0 <3.2.0
Fixed in
3.2.0
Update to the fixed version for your release line, for example:pip install 'apache-airflow-core>=3.2.0'

Details

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.

Is GHSA-h97w-pm3w-mwmc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected apache-airflow-core, and gives you the command that fixes it.

More advisories for apache-airflow-core

  • HighCVE-2026-49298Apache Airflow: Execution API JWT leaked via KubernetesExecutor worker command-line args · 1 Jun 2026
  • HighCVE-2026-25917Apache Airflow allows code execution through crafted XCom payloads · 18 Apr 2026
  • MediumCVE-2026-30912Apache Airflow exposes SQL stack trace despite "api/expose_stack_traces" set to false · 18 Apr 2026
  • LowCVE-2026-32690Apache Airflow Exposes Secrets in Variables Saved as JSON Dictionaries · 18 Apr 2026
apache-airflow-core security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.