# CVE-2026-6064: Norton, Avast, and AVG local privilege escalation via link following in Data Shredder


- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5qpm-4cp9-qch8

## What is CVE-2026-6064?

CVE-2026-6064 is a high-severity vulnerability in Gen Digital AVG Internet Security, published on 28 Oct 2026. 

### Official description

Link following vulnerability in Data Shredder components in Norton Antivirus, Avast Antivirus, and AVG Internet Security prior to 26.5.10933 on Windows allows a local, low-privileged attacker to escalate privileges to SYSTEM. During a privileged shred operation, enabling arbitrary file/folder deletion that is leveraged to gain NT AUTHORITY\SYSTEM privelages.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-6064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6064 is a high-severity vulnerability in Gen Digital AVG Internet Security, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-6064 in the wild and no public exploit code.

Affected product: Gen Digital AVG Internet Security. 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-6064/ (Markdown: https://insights.sbomify.com/CVE-2026-6064/index.md)
```

## Sources

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

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