# CVE-2025-14601: vsDesk Task Scheduler OS Command Injection

> Authenticated administrators can execute arbitrary OS commands in vsDesk Task Scheduler due to insufficient input filtering, potentially leading to full server compromise.

- **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
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-mjxg-34vj-37wc

## What is CVE-2025-14601?

CVE-2025-14601 is a high-severity command injection 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 OS command injection vulnerability in vsDesk allows an authenticated attacker with administrative privileges to execute arbitrary operating system commands due to insufficient input filtering. An attacker can exploit this flaw to disrupt web server operations, expose sensitive data, or potentially achieve full server compromise.

Apply patch from vendor  https://vsdesk.ru/ . Versions 14.0101 and on have the patch.

Weakness: CWE-676 (Use of Potentially Dangerous Function)

## Which versions are affected by CVE-2025-14601?


## How do I fix CVE-2025-14601?

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

## Is CVE-2025-14601 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14601 and fix it if it is affected.

What it is: CVE-2025-14601 is a high-severity command injection 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-2025-14601 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-2025-14601/ (Markdown: https://insights.sbomify.com/CVE-2025-14601/index.md)
```

## Sources

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

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