ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-42359

A bug in Apache Airflow's XCom PATCH endpoint allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g.

Published Jun 1, 2026 · catalog updated Jul 21, 2026 · the affected product

Check if you run it

No confirmed exploitation is on record for CVE-2026-42359. EPSS is 0.95%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.95%
Remediation
Advisory link
Affected products
cpe apache/airflow

A bug in Apache Airflow's XCom PATCH endpoint allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g. ) that the matching POST endpoint already validated against . 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 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 3.2.2 or later to cover the PATCH-path bypass.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/airflowversion unspecified

How to fix CVE-2026-42359

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-42359. EPSS is 0.95%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-502: Deserialization of Untrusted Data. EPSS 0.95%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 1, 2026 · NIST NVD

    Detected

    A bug in Apache Airflow's XCom PATCH endpoint allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g. ) that the matching POST endpoint already validated against . 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 nex

  2. Jul 21, 2026 · NIST NVD

    Updated

    A bug in Apache Airflow's XCom PATCH endpoint allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g. ) that the matching POST endpoint already validated against . 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 nex

Sources

  • CVE.orgVulnerability recordCVE-2026-42359

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-42359

    30-day exploitation probability 0.9%

    first.org
  • NIST NVDVulnerability recordCVE-2026-42359

    A bug in Apache Airflow's XCom PATCH endpoint allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e.g. ) that the matching POST endpoint already validated against `F

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.