Apache Airflow XCom Endpoint Bypass Enables Remote Code Execution

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 419matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-42359 is a critical authentication bypass vulnerability in Apache Airflow's XCom PATCH endpoint that allows authenticated users to circumvent security restrictions and achieve remote code execution. The vulnerability exploits a gap between two endpoints: while the POST endpoint validates against reserved XCom key names like `return_value`, the PATCH endpoint lacks this validation, permitting attackers to write malicious serialized payloads to restricted keys. When a deferred task executes, the triggerer deserializes these payloads, treating them as executable code and granting attackers RCE on the triggerer process. This affects any Apache Airflow deployment where users have XCom write permissions, making it particularly dangerous in multi-tenant environments or organizations with broad user access policies.

Casky's 419 mapped security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Initial Access), TA0043 (Reconnaissance), and TA0002 (Execution). Practitioners using Casky would identify suspicious activity through skills detecting: (1) unusual PATCH requests to `/api/v2/xcomEntries/` endpoints with restricted key names in request bodies, (2) authentication context validation failures where authenticated users attempt operations beyond their intended scope, (3) serialized object patterns in API payloads that match deserialization gadget chains, and (4) downstream execution anomalies on triggerer processes following XCom writes. The platform's correlation of these signals across execution and privilege escalation techniques helps practitioners distinguish legitimate Airflow operations from exploitation attempts, enabling rapid detection and containment of in-progress attacks.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

419 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-42359.

analyzing-android-malware-with-apktool

malware analysis · medium

Run

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-bootkit-and-rootkit-samples

malware analysis · medium

Run

MITRE ATT&CK Techniques

TA0001 TA0043 TA0002

Investigate the attack patterns behind CVE-2026-42359

Casky has 419 skills that investigate the attack patterns behind CVE-2026-42359. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn