# CVE-2026-2334: ) Missing Server-Side File Extension Validation in vsDesk

> An authenticated administrator can upload arbitrary files via CSV import due to missing server-side validation, leading to remote code execution.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-cxgp-6h9c-hfpc

## What is CVE-2026-2334?

CVE-2026-2334 is a critical vulnerability in vsDesk, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in vsDesk v14.0101. An authenticated attacker with administrative privileges can bypass client-side file validation in the "Import via CSV" component due to a lack of server-side validation. This allows the upload of an arbitrary file, which can lead to Remote Code Execution (RCE) within the context of the web application. 
Apply patch from vendor  https://vsdesk.ru/ . Versions 14.0402 and on have the patch.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-2334 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2334 is a critical vulnerability in vsDesk, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2334 in the wild and no public exploit code.

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

## Sources

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

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