# CVE-2026-56137: Command injection in RPG MAKER MV

> Attackers can execute arbitrary OS commands by tricking users into loading a specially crafted save file in RPG MAKER MV or MZ.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-f7jr-jmf8-58m2

## What is CVE-2026-56137?

CVE-2026-56137 is a high-severity command injection vulnerability in Gotcha Gotcha Games Inc. RPG MAKER MV, published on 30 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

RPG MAKER MV and MZ provided by Gotcha Gotcha Games Inc. contain an OS command injection vulnerability. If a user loads a specially crafted save-file, arbitrary OS command may be executed.

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

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


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

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

## Is CVE-2026-56137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56137 is a high-severity command injection vulnerability in Gotcha Gotcha Games Inc. RPG MAKER MV, published on 30 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-56137 in the wild and no public exploit code.

Affected product: Gotcha Gotcha Games Inc. RPG MAKER MV. 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-56137/ (Markdown: https://insights.sbomify.com/CVE-2026-56137/index.md)
```

## Sources

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

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