# CVE-2025-14602: Weak File Name Generation in vsDesk

> Remote attackers can predict uploaded file names to access sensitive files, potentially facilitating further attacks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-2vv3-69qg-3hgr

## What is CVE-2025-14602?

CVE-2025-14602 is a medium-severity vulnerability in vsDesk, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The application generates uploaded file names using a weak and predictable method based on the request timestamp. This allows a remote attacker to accurately guess or brute-force the generated filename within a short time window. An attacker can successfully locate and access uploaded files, which can be used to facilitate further attacks.

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

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File), CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2025-14602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14602 is a medium-severity vulnerability in vsDesk, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14602 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-14602/ (Markdown: https://insights.sbomify.com/CVE-2025-14602/index.md)
```

## Sources

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

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