XCom poisoning via disabled-pickling fallback
Published Jan 24, 2024 · Updated May 30, 2025
Unsafe deserialization in Apache Airflow before 2.8.1 allows remote authenticated users to poison XCom data through authored DAGs. The XCom _deserialize_value routine falls back to pickle.loads when JSON decoding fails, even when enable_xcom_pickling is false. DAG-author privileges are required; crafted non-JSON XCom bytes then reach Python pickle deserialization despite the disabled setting.
Summary
What happened
Unsafe deserialization in Apache Airflow before 2.8.1 allows remote authenticated users to poison XCom data through authored DAGs. The XCom _deserialize_value routine falls back to pickle.loads when JSON decoding fails, even when enable_xcom_pickling is false. DAG-author privileges are required; crafted non-JSON XCom bytes then reach Python pickle deserialization despite the disabled setting.
The record
- CVE
- CVE-2023-50943
- Published
- Jan 24, 2024
- Updated
- May 30, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-502, T1059.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo