Apache Airflow's XCom `GET /api/v2/{...}/xcomEntries/{key}?deserialize=true` endpoint passed a string-literal payload through `BaseXCom.deserialize_value` without the `_check_forbidden_xcom_keys` 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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/69378 Issue Tracking, Patch
- https://lists.apache.org/thread/dm0520yhh4mn7qknyoh45r2w6c5qg2mg Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.4 · apacheNVD modified 2026-10-23 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/69378 Issue Tracking, Patch
- https://lists.apache.org/thread/dm0520yhh4mn7qknyoh45r2w6c5qg2mg Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/08/12/6 Mailing List, Third Party Advisory