CVE-2026-82964

Avast sandbox privilege escalation via unpreserved DACLs on virtualized files in aswSnx.sys

HIGH
8.8
CVSS Score
Published: September 16, 2026 at 02:01 PM UTC
Updated: September 17, 2026 at 07:17 PM UTC
12 products affected across 1 vendorAvast OneAVG Internet SecurityAvast Business Security

Using Avast Free Antivirus, Avast One, Avast Premium Security, Avast Ultimate, Avast Business Security by Gen Digital?

Get instant alerts when new vulnerabilities affect Avast Free Antivirus, Avast One, Avast Premium Security, Avast Ultimate, Avast Business Security - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

Improper preservation of permissions in the Avast sandbox minifilter driver (aswSnx.sys) on Windows allows a local, low-privileged attacker executing inside the sandbox to escape file isolation and escalate to SYSTEM. When the sandbox virtualizes a file it copies the original security descriptor, but the driver opened the virtualization target object with GENERIC_WRITE and FILE_WRITE_ATTRIBUTES only, omitting WRITE_DAC. Every attempt to apply the original DACL therefore failed, and the failure was discarded silently, leaving virtualized copies of sensitive files with permissive permissions. Because the IRP_MJ_CREATE callback additionally did not strip WRITE_DAC for sensitive directories, a sandboxed process could rewrite the security descriptor of a virtualized object, read the virtualized copy of the SAM database, extract local NTLM password hashes and execute code as SYSTEM. The absence of an IRP_MJ_SET_SECURITY callback in the driver's operation registration table is a related defense-in-depth gap, but it is not the control that prevents this attack.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement
v < 26.8
Affected range stops below 26.8, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHGEN
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-281CWE-653CWE-862

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card