CVE-2026-42359

published 1 Jun 2026 · updated 3 Nov 2026

Apache Airflow: Authenticated RCE via XCom PATCH endpoint — XComUpdateBody missing FORBIDDEN_XCOM_KEYS validator

8.8HighCVSS 8.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Airflow 3.2.2 and 3.2.2.

A bug in Apache Airflow's XCom PATCH endpoint `PATCH /api/v2/xcomEntries/{key}` allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g. `return_value`) that the matching POST endpoint already validated against `FORBIDDEN_XCOM_KEYS`. The endpoint also accepted serialized payload shapes the triggerer's deserializer treats as code; combined, this allowed RCE on the triggerer when the affected task next deferred. Affects deployments where untrusted users have XCom write permission on Dags that defer to the triggerer. This is a fix-bypass of CVE-2026-33858: PR #64148 added the `FORBIDDEN_XCOM_KEYS` validator only on the POST/set path; the PATCH path was not covered. Users who already upgraded for CVE-2026-33858 should additionally upgrade to `apache-airflow` 3.2.2 or later to cover the PATCH-path bypass.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheAirflow>=3.2.0 <3.2.23.2.2
Apache Software Foundation>=3.2.0 <3.2.23.2.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Airflow, strongest first

10.0CriticalCISA KEVPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-42359 severity on Zeptric[![CVE-2026-42359](https://zeptric.io/badge/cve/CVE-2026-42359.svg)](https://zeptric.io/cve/CVE-2026-42359)