# CVE-2026-118755: Volmarg Personal Management System through 2.1.0 OS Command Injection via Storage Folder Path


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-pq7g-3p4f-wvm7

## What is CVE-2026-118755?

CVE-2026-118755 is a high-severity vulnerability in Volmarg personal-management-system, published on 28 Oct 2026. 

### Official description

Volmarg Personal Management System through 2.1.0 contains an OS command injection vulnerability that allows authenticated users to execute shell commands via unescaped folder paths in the storage module's tree command. Attackers can create a directory under upload/files containing shell metacharacters such as $(...) and then move or copy it, running commands as the web server user.

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

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


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

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

## Is CVE-2026-118755 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118755 is a high-severity vulnerability in Volmarg personal-management-system, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118755 in the wild and no public exploit code.

Affected product: Volmarg personal-management-system. 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-118755/ (Markdown: https://insights.sbomify.com/CVE-2026-118755/index.md)
```

## Sources

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

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