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

> An authenticated local user can exploit improper access control in the kernel driver to gain SYSTEM privileges on Seclore FileSecure Desktop Client.

- **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:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-w2x4-mxjr-6f86

## What is CVE-2026-79153?

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

### Official description

Seclore FileSecure Desktop Client before 3.25.1.0 contains improper access control vulnerability in the kernel-mode driver component that allows an authenticated local user to gain elevated privileges to NT AUTHORITY\SYSTEM on affected systems.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-79153 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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