# CVE-2025-63946: Race condition in n/a

> A local attacker can exploit a race condition in Tencent PC Manager to execute programs with elevated privileges, leading to privilege escalation.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-fqqc-4836-hph4

## What is CVE-2025-63946?

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

### Official description

A privilege escalation (PE) vulnerability in the Tencent PC Manager app thru 17.10.28554.205 on Windows devices enables a local user to execute programs with elevated privileges. However, execution requires that the local user is able to successfully exploit a race condition.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Tencent Pcmanager.

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

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

## Is CVE-2025-63946 being exploited?

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

Public exploit code:

- https://github.com/alexlee820/CVE-2025-63946-Tencent-PC-Manager-EoP (github_poc): https://github.com/alexlee820/CVE-2025-63946-Tencent-PC-Manager-EoP

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63946 is a high-severity vulnerability in n/a, published on 23 Feb 2026. 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-63946 in the wild and no public exploit code.

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-63946/ (Markdown: https://insights.sbomify.com/CVE-2025-63946/index.md)
```

## Sources

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

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