# CVE-2026-119025: open 7.2.0 before 11.0.0 OS Command Injection via PowerShell on Windows


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/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
- **Also known as:** GHSA-jgwm-4pmq-r4w4, GHSA-q978-78c7-phqw

## What is CVE-2026-119025?

CVE-2026-119025 is a high-severity vulnerability in anomalyco inspector, published on 29 Oct 2026. 

### Official description

open 7.2.0 before 11.0.0 contains an OS command injection vulnerability that allows attackers to execute PowerShell code by supplying crafted URLs on Windows and WSL. Attackers can embed $(...) subexpressions in URLs, such as OAuth authorization_endpoint values from malicious MCP servers, which execute when index.js passes them unescaped to powershell -EncodedCommand.

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

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


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

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

## Is CVE-2026-119025 being exploited?

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

Public exploit code:

- Trace untrusted OAuth endpoint URLs from source to shell sink — the CVE-2026-119025 attack class, checked in your code, lockfile and MCP configs. (github_poc): https://github.com/shouvikkkk/oauth-sink-check

## Fix prompt for AI coding agents

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

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

Affected product: anomalyco inspector. 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-119025/ (Markdown: https://insights.sbomify.com/CVE-2026-119025/index.md)
```

## Sources

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

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