Description
An example of BashOperator in Airflow documentation suggested a way of passing dag_run.conf in the way that could cause unsanitized user input to be used to escalate privileges of UI user to allow execute code on worker. Users should review if any of their own DAGs have adopted this incorrect advice.
Published: 2026-04-18
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution
Action: Assess Impact
AI Analysis

Impact

Based on the description, an example in the Apache Airflow documentation shows that passing user‑provided dag_run.conf values directly into a BashOperator can cause unsanitized input to be executed as shell commands. The vulnerability is a classic command injection scenario (CWE‑77). If successfully exploited, an attacker could run arbitrary code on the worker that executes the DAG, effectively gaining remote code execution privileges on that host.

Affected Systems

All Apache Airflow installations that have adopted the documented pattern for passing dag_run.conf values to the BashOperator are potentially affected. No specific product version was listed in the advisory, so the risk applies broadly to deployments that follow the insecure pattern.

Risk and Exploitability

The likely attack vector is through the Airflow web UI or API by supplying crafted dag_run.conf data for a DAG that uses the BashOperator. Because the conf data is concatenated directly into the shell command, a single malicious entry can execute arbitrary commands with the privileges of the worker process. The CVSS score is not disclosed in the advisory, so the precise severity level cannot be quantified, but the vulnerability could enable remote code execution. EPSS is reported as <1%, indicating a low exploitation probability, and the issue is not listed in the CISA KEV catalog.

Generated by OpenCVE AI on April 18, 2026 at 19:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Review all DAGs that use BashOperator and verify whether dag_run.conf values are directly passed to the shell command.
  • Sanitise or escape all dag_run.conf inputs before they reach the BashOperator, or use safe parameterisation alternatives such as templating or argument lists.
  • Restrict or disable the ability for untrusted users to submit dag_run.conf through the UI for DAGs that run with elevated privileges.
  • Check for and apply any newer Apache Airflow releases that address this issue, even if the advisory does not list an explicit patch.

Generated by OpenCVE AI on April 18, 2026 at 19:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 18 Apr 2026 09:15:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache airflow
Vendors & Products Apache
Apache airflow

Sat, 18 Apr 2026 07:30:00 +0000

Type Values Removed Values Added
References

Sat, 18 Apr 2026 07:00:00 +0000

Type Values Removed Values Added
Description An example of BashOperator in Airflow documentation suggested a way of passing dag_run.conf in the way that could cause unsanitized user input to be used to escalate privileges of UI user to allow execute code on worker. Users should review if any of their own DAGs have adopted this incorrect advice.
Title Apache Airflow: Bad example of BashOperator shell injection via dag_run.conf
Weaknesses CWE-77
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-04-18T06:28:55.918Z

Reserved: 2026-03-06T16:58:56.509Z

Link: CVE-2026-30898

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-04-18T07:16:10.297

Modified: 2026-04-18T07:16:10.297

Link: CVE-2026-30898

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-18T19:30:08Z

Weaknesses