# CVE-2026-3680: RyuzakiShinji biome-mcp-server biome-mcp-server.ts command injection

> Remote attackers can execute arbitrary commands via command injection in the biome-mcp-server tool, requiring a patch to mitigate.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-hr3g-62w3-g764

## What is CVE-2026-3680?

CVE-2026-3680 is a medium-severity command injection vulnerability in RyuzakiShinji biome-mcp-server, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in RyuzakiShinji biome-mcp-server up to 1.0.0. Affected by this issue is some unknown functionality of the file biome-mcp-server.ts. Performing a manipulation results in command injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The patch is named 335e1727147efeef011f1ff8b05dd751d8a660be. Applying a patch is the recommended action to fix this issue.

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-3680?


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

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

## Is CVE-2026-3680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3680 is a medium-severity command injection vulnerability in RyuzakiShinji biome-mcp-server, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3680 exists.

Affected product: RyuzakiShinji biome-mcp-server. 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-3680/ (Markdown: https://insights.sbomify.com/CVE-2026-3680/index.md)
```

## Sources

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

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