Vulnerability · CVE-2026-42252
Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning.
Published Jun 1, 2026 · corrected/updated Jul 21, 2026 · apache airflow · evidence confidence medium
Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the field of the trigger API: an authenticated trigger user could supply as a value and reach an on the worker. This CVE covers the documentation correction in PR 64129 — the pattern in the docs example now includes explicit shell-quoting and a safety caveat. Affects deployments whose Dag code was modeled on the pre-correction docs example. Same class as the prior CVE-2025-50213 and CVE-2025-27018 documentation-pattern fixes. Users are advised to upgrade to 3.2.2 or later to pick up the corrected documentation shipped with the release.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-42252 is a critical public vulnerability record for apache airflow. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether apache airflow is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: apache/airflow. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 9.1. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-1336. Sources contributing to this record: nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jun 1, 2026 · NIST NVD
Detected
Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the fie
Jul 21, 2026 · NIST NVD
Updated
Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the fie
Affected
- cpe apache/airflowversion unspecified
Sources
- NIST NVDVulnerability recordCVE-2026-42252
Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning. Dag authors who copied
nvd.nist.gov