# CVE-2025-10539: Improper TLS Certificate Validation RCE via Malicious Update in DeskTime Time Tracking App

> Attackers can achieve remote code execution by intercepting update requests due to improper TLS certificate validation in the DeskTime desktop application.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-m272-rh3v-6hfm

## What is CVE-2025-10539?

CVE-2025-10539 is a medium-severity vulnerability in DeskTime Time Tracking App, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to improper TLS certificate validation in the DeskTime Time Tracking App before version 1.3.674, attackers who can position themselves in the network path between the client and the DeskTime update servers can return a malicious executable in response to an update request. This allows the attacker to achieve user-level remote code execution on the affected client.

Weakness: CWE-494 (Download of Code Without Integrity Check), CWE-296 (Improper Following of a Certificate's Chain of Trust), CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Draugiemgroup Desktime Time Tracking.

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

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

## Is CVE-2025-10539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10539 is a medium-severity vulnerability in DeskTime Time Tracking App, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10539 exists.

Affected product: DeskTime Time Tracking App. 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-10539/ (Markdown: https://insights.sbomify.com/CVE-2025-10539/index.md)
```

## Sources

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

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