# CVE-2025-66835: Other in n/a

> Local attackers can execute arbitrary code in the user's context via DLL hijacking in TrueConf Client.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 30 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-vrjf-962m-57c2

## What is CVE-2025-66835?

CVE-2025-66835 is a high-severity vulnerability in n/a, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TrueConf Client 8.5.2 is vulnerable to DLL hijacking via crafted wfapi.dll allowing local attackers to execute arbitrary code within the user's context.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Trueconf Trueconf.

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

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

## Is CVE-2025-66835 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-3502](https://insights.sbomify.com/CVE-2026-3502/): TrueConf Client Download of Code Without Integrity Check (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66835 is a high-severity vulnerability in n/a, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66835 exists.

Affected product: n/a. 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-66835/ (Markdown: https://insights.sbomify.com/CVE-2025-66835/index.md)
```

## Sources

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

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