# CVE-2025-58074: Privilege escalation during the installation of Norton Secure VPN via the Microsoft Store

> A low-privilege user can escalate privileges by replacing files during the installation of Norton Secure VPN via the Microsoft Store.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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:** 4 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-7wj7-3wwj-fhf7

## What is CVE-2025-58074?

CVE-2025-58074 is a high-severity vulnerability in Gen Digital Norton Secure VPN, published on 4 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability exists during the installation of Norton Secure VPN via the Microsoft Store. A low-privilege user can replace files during the installation process, which may result in deletion of arbitrary files that can lead to elevation of privileges.

Weakness: CWE-1386 (Insecure Operation on Windows Junction / Mount Point)

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


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

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

## Is CVE-2025-58074 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58074 is a high-severity vulnerability in Gen Digital Norton Secure VPN, published on 4 May 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-2025-58074 in the wild and no public exploit code.

Affected product: Gen Digital Norton Secure VPN. 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-58074/ (Markdown: https://insights.sbomify.com/CVE-2025-58074/index.md)
```

## Sources

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

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