# @nx/docker: OS command injection in the @nx/docker release pipeline Advisory record · `GHSA-6vc5-vf29-ffr2` - **Identifiers:** `GHSA-6vc5-vf29-ffr2` · `CVE-2026-104859` - **State:** Confirmed - **Severity:** CVSS 7.3 High - **Critical:** No - **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html) - **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md) - **Published:** 5 Oct 2026 - **Updated:** 5 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 5 Oct 2026, 23:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `@nx/docker` (npm): affected `>=21.4.0, <22.7.8 || >=23.0.0, <23.1.1`; fixed in `22.7.8`, `23.1.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The @nx/docker package is vulnerable in versions from 21.4.0 up to 22.7.8 and from 23.0.0 up to 23.1.1. An attacker who can supply a crafted Docker repository or registry name in Nx configuration, such as through a pull request that changes it, can get that value run as a shell command during nx release version or nx release publish, with the release job's privileges. Upgrade to 22.7.8 for the 22.x line or 23.1.1 for the 23.x line; the source says the fix needs no configuration change, and notes that --dry-run does not prevent the injected command from running. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.3 High, CVSS 4.0: `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`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0015, the 4th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:34 UTC: First seen by agentprime - 31 Oct 2026, 13:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6vc5-vf29-ffr2) ## Sources - [GitHub Advisory Database: GHSA-6vc5-vf29-ffr2](https://github.com/advisories/GHSA-6vc5-vf29-ffr2) - [OSV: GHSA-6vc5-vf29-ffr2](https://osv.dev/vulnerability/GHSA-6vc5-vf29-ffr2) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .