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

CVE-2026-32228 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Apache Airflow are affected by CVE-2026-32228?

Apache Airflow 3.0.x through 3.1.x contains a privilege escalation vulnerability allowing attackers to trigger unauthorized DAG execution by bypassing asset materialize permission checks.. A patch is available.

How to fix or mitigate CVE-2026-32228?

Within 24 hours: Inventory all Apache Airflow deployments and identify those running versions 3.0.x through 3.1.x. Within 7 days: Apply vendor-released patch to upgrade Apache Airflow to version 3.2.0 or later across all affected environments. Within 30 days: Conduct access control audit to verify asset materialize permissions are correctly enforced and review DAG execution logs for unauthorized activity during the vulnerable period.

Apache Airflow CVE-2026-32228

EUVD-2026-23664 HIGH

Incorrect Authorization (CWE-863)

2026-04-18 apache

GHSA-h97w-pm3w-mwmc

Authentication Bypass Apache Airflow

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Updated

Apr 21, 2026 - 13:12 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Apr 20, 2026 - 19:07 vuln.today

cvss_changed

Analysis Generated

Apr 20, 2026 - 16:23 vuln.today

CVSS changed

Apr 20, 2026 - 16:22 NVD

7.5 (HIGH)

EUVD ID Assigned

Apr 18, 2026 - 07:00 euvd

EUVD-2026-23664

Analysis Generated

Apr 18, 2026 - 07:00 vuln.today

Patch released

Apr 18, 2026 - 07:00 nvd

Patch available

CVE Published

Apr 18, 2026 - 06:19 nvd

HIGH 7.5

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

4 pypi packages depend on apache-airflow-core (2 direct, 2 indirect)

Ecosystem-wide dependent count for version 3.0.0.

DescriptionCVE.org

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.

AnalysisAI

Apache Airflow 3.0.x prior to 3.2.0 allows remote unauthenticated attackers to trigger unauthorized DAG (Directed Acyclic Graph) execution via the UI or API, bypassing asset materialize permission checks. Despite CVSS 7.5 HIGH, the CVSS vector (PR:N) contradicts the description's requirement for 'UI/API user with asset materialize permission', suggesting authentication IS required-a critical discrepancy that demands verification. EPSS of 0.01% (3rd percentile) indicates minimal observed exploitation activity. Vendor-released patch available in Airflow 3.2.0 per Apache advisory.

Technical ContextAI

Apache Airflow is a workflow orchestration platform where DAGs define task dependencies and execution schedules. This vulnerability stems from CWE-863 (Incorrect Authorization), specifically in the asset materialization feature introduced in Airflow 3.0.x. The flaw occurs when users holding 'asset materialize' permissions interact with the UI or REST API-the authorization check incorrectly validates the materialize permission but fails to verify DAG-level execution permissions. This broken access control allows authenticated users to trigger execution of DAGs outside their assigned scope. The affected component is the asset materialization workflow handler, likely in the API endpoint or UI controller responsible for processing materialization requests. CPE identifies the vulnerability in apache_software_foundation:apache_airflow across the 3.0.x branch.

RemediationAI

Upgrade Apache Airflow to version 3.2.0 or later, which contains the authorization check fix per Apache Security Team advisory (https://lists.apache.org/thread/s7c75txgt4qf2rofcn43szfwgcrzy0nj). The fix is implemented in GitHub pull request #63338 (https://github.com/apache/airflow/pull/63338). For environments unable to immediately upgrade, implement compensating controls: restrict access to the Airflow UI and API endpoints to only fully trusted users by enforcing network segmentation (e.g., limit access to internal VPN or bastion hosts); disable the asset materialization feature entirely if not business-critical by removing asset materialize permissions from all user roles and blocking related API endpoints at the reverse proxy layer (note: this eliminates the feature's functionality); audit existing DAG execution logs for unauthorized triggers by correlating user permissions with executed DAG IDs over the past 90 days to identify potential prior exploitation. These workarounds reduce attack surface but do not eliminate the underlying authorization flaw-upgrade remains the definitive remediation.