# CVE-2026-16133: LiuMengxuan04 MiniCode mcp.ts child_process.spawn command injection

> Remote attackers can execute arbitrary commands via command injection in MiniCode's MCP module, requiring high complexity but posing code execution risks.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-9gx9-7vc6-hh65

## What is CVE-2026-16133?

CVE-2026-16133 is a low-severity command injection vulnerability in LiuMengxuan04 MiniCode, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in LiuMengxuan04 MiniCode 0.1.0. Affected by this vulnerability is the function child_process.spawn of the file mcp.ts. Executing a manipulation can lead to command injection. The attack can be launched remotely. The attack requires a high level of complexity. The exploitation appears to be difficult. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-16133 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16133 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16133 is a low-severity command injection vulnerability in LiuMengxuan04 MiniCode, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16133 exists.

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

## Sources

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

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