cve.bz

CVE-2026-59242 apache airflow: Deserialization of Untrusted Data

5.4 mediumEPSS 0.5%Fix available

Medium (5.4) in apache airflow. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow 3.3.1.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-59242 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59242?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59242?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59242 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-59242

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-59242](https://cve.bz/cve/badge/CVE-2026-59242.svg)](https://cve.bz/cve/CVE-2026-59242)

HTML:

<a href="https://cve.bz/cve/CVE-2026-59242"><img src="https://cve.bz/cve/badge/CVE-2026-59242.svg" alt="CVE-2026-59242"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowbefore 3.0.0
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.3.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fcmm-42r9-mmmmPyPIapache-airflow<3.3.13.3.1
PYSEC-2026-3992PyPIapache-airflow<3.3.13.3.1

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON