CVE-2026-33858
8.8Apache · Airflow
An authenticated Dag Author can craft a malicious XCom payload to execute arbitrary code within the webserver context due to insecure deserialization of untrusted data.
Executive summary
A vulnerability in Apache Airflow allows authenticated Dag Authors to achieve remote code execution, posing a significant risk to the integrity and availability of the webserver environment.
Vulnerability
This flaw involves CWE-502: Deserialization of Untrusted Data, which allows a user with Dag Author privileges to bypass existing restrictions and execute arbitrary code on the webserver. The attack vector is network-based and requires low privileges, as indicated by the CVSS vector PR:L.
Business impact
Successful exploitation permits an attacker to execute arbitrary code with the permissions of the webserver, potentially leading to full system compromise, unauthorized data access, and lateral movement within the infrastructure. While the vendor notes that Dag Authors are often considered trusted, the ability to escalate privileges to code execution represents a critical failure in the application boundary that could lead to widespread operational disruption.
Remediation
Immediate Action: Upgrade to Apache Airflow version 3.2.0 or later to apply the necessary security patches and resolve the deserialization vulnerability.
Proactive Monitoring: Monitor webserver logs for suspicious XCom activity or unexpected payload structures that deviate from standard DAG execution patterns.
Compensating Controls: Implement strict access control policies to limit the number of users with Dag Author permissions and ensure that the webserver process runs with the least privilege necessary to perform its functions.
Exploitation status
Public Exploit Available: No
Analyst recommendation
Given the potential for remote code execution, organizations should prioritize upgrading their Apache Airflow instances to version 3.2.0. Even if users are considered trusted, the risk of credential compromise or insider threats necessitates the immediate removal of this attack vector from the production environment.
More Apache CVEs
Sources
Originally found and disclosed by wooseokdotkim, with Amogh Desai (remediation developer), per the CVE Program record.