# CVE-2026-12195: Command injection in vesta

> Low-privileged users can execute arbitrary commands as admin via FTP username deletion, leading to full system compromise.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **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:** 4 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-233w-5rfj-8hmj

## What is CVE-2026-12195?

CVE-2026-12195 is a high-severity command injection vulnerability in myvesta vesta, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

myVesta is affected by an authenticated remote code execution vulnerability. Low privileged users can insert arbitrary commands as a part of the v_ftp_user parameter when deleting FTP usernames. This could result in the execution of commands as the admin user or takevoer of the admin user in myVesta.

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

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


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

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

## Is CVE-2026-12195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12195 is a high-severity command injection vulnerability in myvesta vesta, published on 4 Jul 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-12195 exists.

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

## Sources

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

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