# CVE-2026-48787: gin-vue-admin vulnerable to RCE

> Authenticated attackers can inject Go code via the code-generation feature to execute arbitrary OS commands on the server.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-22cv-9jv2-6m62

## What is CVE-2026-48787?

CVE-2026-48787 is a high-severity code injection vulnerability in flipped-aurora gin-vue-admin, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

gin-vue-admin is an AI-assisted basic development platform. In version 2.9.1, an authenticated attacker with access to the code-generation feature and MCP management interface can exploit this vulnerability by injecting attacker-controlled Go source code through POST /autoCode/addFunc, and then invoking POST /autoCode/mcpStart to trigger a rebuild and restart of the standalone MCP service. This allows arbitrary operating system commands to be executed on the server with the privileges of the application process. Successful exploitation may lead to remote code execution (RCE), modification of backend source code or runtime logic, deployment of persistent backdoors, access to or manipulation of application data and configuration, and further impact on local resources running under the same service account or privilege context. The risk is highest in deployments that retain the source tree, allow writes to source files, and support local build or startup of standalone MCP components. In environments using binary-only releases, read-only filesystems, or with local build capabilities removed, the exploitability of the full attack chain is significantly reduced. However, once the online code-generation capability and MCP-hosted startup workflow are enabled, the overall security impact may reach high to critical severity. As of time of publication, it is unknown if a patched version is available. As a workaround, enforce strict allowlist validation on path- and identifier-related fields such as `humpPackageName`, `packageName`, `FuncName`, and `Router`, and only permit safe identifier formats.

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

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


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

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

## Is CVE-2026-48787 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48787 is a high-severity code injection vulnerability in flipped-aurora gin-vue-admin, published on 19 Jun 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-48787 exists.

Affected product: flipped-aurora gin-vue-admin. 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-48787/ (Markdown: https://insights.sbomify.com/CVE-2026-48787/index.md)
```

## Sources

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

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