# CVE-2026-114492: gin-vue-admin through 2.9.2 Path Traversal via removePlugin Endpoint


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-mqv7-9mvf-h9fh, GHSA-qgwp-mwx4-c64g

## What is CVE-2026-114492?

CVE-2026-114492 is a high-severity vulnerability in flipped-aurora gin-vue-admin, published on 21 Oct 2026. 

### Official description

gin-vue-admin through 2.9.2 contains a path traversal vulnerability that allows authenticated administrators to recursively delete arbitrary directories by supplying traversal sequences in the pluginName parameter. Attackers can send a crafted POST request to /autoCode/removePlugin with '../' sequences, causing os.RemoveAll to delete any directory writable by the server process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-114492 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114492 is a high-severity vulnerability in flipped-aurora gin-vue-admin, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114492 in the wild and no public exploit code.

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-114492/ (Markdown: https://insights.sbomify.com/CVE-2026-114492/index.md)
```

## Sources

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

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