# CVE-2025-64699: Missing authorization in n/a

> An incorrect NULL DACL in SevenCs ORCA G2 allows attackers to perform unauthorized raw disk operations, leading to privilege escalation, data exposure, and system disruption.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-p62x-cp56-r6pr

## What is CVE-2025-64699?

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

### Official description

An incorrect NULL DACL issue exists in SevenCs ORCA G2 2.0.1.35 (EC2007 Kernel v5.22). The regService process, which runs with SYSTEM privileges, applies a Security Descriptor to a device object with no explicitly configured DACL. This condition could allow an attacker to perform unauthorized raw disk operations, which could lead to system disruption (DoS) and exposure of sensitive data, and may facilitate local privilege escalation.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 2 products.


Products: Sevencs Ec2007 Kernel, Sevencs Orca G2.

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

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

## Is CVE-2025-64699 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-61037](https://insights.sbomify.com/CVE-2025-61037/): Race condition in n/a (high 7.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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