# CVE-2026-38766: Privilege escalation in n/a

> A local attacker can escalate privileges in Protegent 360 via a vulnerable function, requiring local access to exploit.

- **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:** 22 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-vcf3-3cgj-wwg5

## What is CVE-2026-38766?

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

### Official description

An issue in Unistal Systems Pvt. Ltd.Protegent 360 v2.0.0.4 allows a local attacker to escalate privileges via the sub_186f4 function

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-38766?


## How do I fix CVE-2026-38766?

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

## Is CVE-2026-38766 being exploited?

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

Public exploit code:

- An issue in Unistal Systems Pvt. Ltd. Protegent 360 v2.0.0.4 allows a local attacker to escalate privileges via a kernel mode driver. (github_poc): https://github.com/D7EAD/CVE-2026-38766

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38766 and fix it if it is affected.

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

## Sources

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

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