# CVE-2026-119282: Nx: OS command injection via nx.json plugin options in @nx/maven and @nx/gradle


- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119282?

CVE-2026-119282 is a high-severity vulnerability in @nx gradle, published on 29 Oct 2026. 

### Official description

Nx is a monorepo solution for TypeScript and polyglot codebases. From 22.0.2 until 22.7.9 and 23.1.2 for @nx/maven, and from 21.0.0 until 22.7.9 and 23.1.2 for @nx/gradle, the plugins' project-graph analyzers launch through a shell and interpolate plugin options from nx.json into command arguments. The @nx/maven targetNamePrefix value and arbitrary @nx/gradle option names or values can therefore be interpreted as shell syntax whenever an nx command constructs the project graph. A user who runs Nx in an attacker-controlled repository or pull request can execute injected commands with the user's privileges, while workspaces that register neither affected plugin are not exposed to this path. Remediation requires upgrading both nx and each affected plugin to matching releases because the plugin fix depends on code in the nx package. This issue is fixed in versions 22.7.9 and 23.1.2.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-119282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119282 is a high-severity vulnerability in @nx gradle, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119282 in the wild and no public exploit code.

Affected product: @nx gradle. 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-119282/ (Markdown: https://insights.sbomify.com/CVE-2026-119282/index.md)
```

## Sources

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

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