# CVE-2026-111422: Apache Airflow SSH provider: SSHRemoteJobOperator: `environment` values are executed as shell on the remote host


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-v5m9-m7pg-q8f3

## What is CVE-2026-111422?

CVE-2026-111422 is a high-severity vulnerability in Apache Airflow SSH provider, published on 26 Oct 2026. 

### Official description

In apache-airflow-providers-ssh before 7.0.1, SSHRemoteJobOperator quoted the values of its templated `environment` parameter only once, although they are placed inside an already-quoted wrapper script, so shell syntax such as `$(...)` in a value was executed on the remote SSH host. In a Dag that passes trigger-time input such as `params` or `dag_run.conf` into `environment`, a user who can trigger that Dag but cannot author Dags could run arbitrary commands on the remote host as the SSH connection's user. Users are advised to upgrade apache-airflow-providers-ssh to 7.0.1 or later.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

No fix has been published for CVE-2026-111422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111422 being exploited?

There is no known exploitation of CVE-2026-111422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111422 and fix it if it is affected.

What it is: CVE-2026-111422 is a high-severity vulnerability in Apache Airflow SSH provider, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111422 in the wild and no public exploit code.

Affected product: Apache Airflow SSH provider. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111422/ (Markdown: https://insights.sbomify.com/CVE-2026-111422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111422
- OSV: https://osv.dev/vulnerability/CVE-2026-111422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111422/
Summaries are generated and may contain mistakes; the official description above is the record.