CVE-2026-59242: Apache Airflow: Arbitrary airflow.* class instantiation on the API server via the XCom deserialize endpoint
Apache Airflow's XCom GET /api/v2/{...}/xcomEntries/{key}?deserialize=true endpoint passed a string-literal payload through BaseXCom.deserializevalue without the checkforbiddenxcomkeys guard, allowing an authenticated API user with XCom write-and-read access to instantiate arbitrary airflow. classes on the API server (CWE-502). An authenticated user who can write an XCom value and then read it back with deserialize=true triggers the unsafe instantiation. Users are advised to upgrade to apache-airflow 3.3.1 or later, which rejects reserved XCom serialization keys submitted as JSON string literals.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
apache-airflowto a version that resolves this vulnerability.Fixed in 3.3.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59242?
CVE-2026-59242 has a risk severity rating of 50.
How do I fix CVE-2026-59242?
To fix CVE-2026-59242, ensure that the `_check_forbidden_xcom_keys` guard is implemented in `BaseXCom.deserialize_value`.
Who is affected by CVE-2026-59242?
Users of Apache Airflow who have authenticated access to the XCom API endpoints are affected by CVE-2026-59242.
What type of attack does CVE-2026-59242 facilitate?
CVE-2026-59242 allows for arbitrary class instantiation via the XCom `GET /api/v2/.../xcomEntries/{key}?deserialize=true` endpoint.
What component of Apache Airflow is impacted by CVE-2026-59242?
The impact of CVE-2026-59242 is on the API server and specifically on the XCom feature.