# CVE-2025-44002: Arbitrary File Creation via Symbolic Link leading to Denial-of-Service

> Local attackers can exploit a race condition to create arbitrary files with SYSTEM privileges, causing denial of service in TeamViewer.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-56qh-f2pg-88cj

## What is CVE-2025-44002?

CVE-2025-44002 is a medium-severity vulnerability in TeamViewer Full Client, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race Condition in the Directory Validation Logic in the TeamViewer Full Client and Host prior version 15.69 on Windows allows a local non-admin user to create arbitrary files with SYSTEM privileges, potentially leading to a denial-of-service condition, via symbolic link manipulation during directory verification.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2025-44002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44002 is a medium-severity vulnerability in TeamViewer Full Client, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-44002 in the wild and no public exploit code.

Affected product: TeamViewer Full Client. 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-44002/ (Markdown: https://insights.sbomify.com/CVE-2025-44002/index.md)
```

## Sources

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

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