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

> Local unprivileged users can escalate privileges to SYSTEM via insecure named pipe access in K7 Ultimate Security.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-33x2-whwf-gwv7

## What is CVE-2025-67826?

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

### Official description

An issue was discovered in K7 Ultimate Security 17.0.2045. A Local Privilege Escalation (LPE) vulnerability in the K7 Ultimate Security antivirus can be exploited by a local unprivileged user on default installations of the product. Insecure access to a named pipe allows unprivileged users to edit any registry key, leading to a full compromise as SYSTEM.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: K7computing K7 Ultimate Security.

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

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

## Is CVE-2025-67826 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16896](https://insights.sbomify.com/CVE-2019-16896/): Path traversal in n/a (high 7.8)
- [CVE-2024-36424](https://insights.sbomify.com/CVE-2024-36424/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67826 is a high-severity vulnerability in n/a, published on 22 Dec 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-67826 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-67826/ (Markdown: https://insights.sbomify.com/CVE-2025-67826/index.md)
```

## Sources

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

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