# CVE-2026-32228: UI / API User with asset materialize permission could trigger dags they had no access to. Users are advised to migrate to Airflow version 3.

Source: https://junglewise.ai/threats/cve-2026-32228-apache-airflow-allows-users-with-asset-materialize-permissions-to  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-18. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-32228 · Severity: high · CVSS 7.5 · Published 2026-04-18

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.

Technologies: [Apache Airflow](https://junglewise.ai/threats/technologies/airflow), [apache-airflow-core (PyPI)](https://junglewise.ai/threats/technologies/apache-airflow-core). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-32228 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-32228 being exploited in the wild.

**How severe is CVE-2026-32228?** High severity, with a CVSS score of 7.5, published 18 April 2026.

**Which products and versions are affected?** apache-airflow-core (PyPI) >= 3.0.0, < 3.2.0, ECOSYSTEM:introduced=3.0.0,fixed=3.2.0.

**Is there a fix for CVE-2026-32228?** Yes. apache-airflow-core (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-32228?** Check whether you run Apache Airflow or apache-airflow-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- apache-airflow-core (PyPI): upgrade to 3.2.0 or later

  ```sh
  pip install "apache-airflow-core>=3.2.0"
  ```


## Affected products

- Apache Airflow
- apache-airflow-core (PyPI) >= 3.0.0, < 3.2.0, ECOSYSTEM:introduced=3.0.0,fixed=3.2.0

## Identifiers

- CVE-2026-32228
- GHSA-h97w-pm3w-mwmc
- PYSEC-2026-2360

## References

- [https://github.com/apache/airflow/pull/63338](https://github.com/apache/airflow/pull/63338)
- [https://lists.apache.org/thread/s7c75txgt4qf2rofcn43szfwgcrzy0nj](https://lists.apache.org/thread/s7c75txgt4qf2rofcn43szfwgcrzy0nj)
- [http://www.openwall.com/lists/oss-security/2026/04/17/8](http://www.openwall.com/lists/oss-security/2026/04/17/8)

## Related threats

- [Apache Airflow incomplete deserialization check bypass in scheduler](https://junglewise.ai/threats/cve-2026-96285-apache-airflow-3-3-1-shipped-a-fix-for-that-checks-the-scheduler)
- [Apache Airflow scheduler XCom deserialization privilege escalation](https://junglewise.ai/threats/cve-2026-86829-apache-airflow-s-scheduler-fully-deserializes-xcom-values-written)
- [Apache Airflow CLI audit log secrets exposure](https://junglewise.ai/threats/cve-2026-86468-apache-airflow-s-cli-records-its-arguments-in-the-audit-log-but)
- [Apache Airflow unsafe deserialization in deadline alert fields](https://junglewise.ai/threats/cve-2026-82337-apache-airflow-rebuilt-deadline-alert-fields-through-generic)
- [Apache Airflow Task SDK secret cache key collision in multi-team deployments](https://junglewise.ai/threats/cve-2026-76185-apache-airflow-s-task-sdk-secret-cache-built-its-keys-from-the)
