# CVE-2025-46014: Privilege escalation in n/a

> Attackers can escalate privileges by exploiting insecure named pipe permissions in Honor PC Manager services.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 30 Jun 2025
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-93ww-rvxc-x7gp

## What is CVE-2025-46014?

CVE-2025-46014 is a high-severity vulnerability in n/a, published on 30 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Several services in Honor Device Co., Ltd Honor PC Manager v16.0.0.118 was discovered to connect services to the named pipe iMateBookAssistant with default or overly permissive security attributes, leading to a privilege escalation.

Weakness: CWE-284 (Improper Access Control), CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Honor Pc Manager.

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

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

## Is CVE-2025-46014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46014 is a high-severity vulnerability in n/a, published on 30 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46014 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-46014/ (Markdown: https://insights.sbomify.com/CVE-2025-46014/index.md)
```

## Sources

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

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