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.
Gen Digital has released a fix as an automatic micro-update to the sandbox driver. No product upgrade or reinstallation is required, and the product version number does not change.
Because the fix replaces a kernel-mode driver, a device restart is required to load it. Until the device is restarted the previous driver stays active and the system remains vulnerable. The application notifies the user to restart.
26.7.1021.026.8.1020.0The update was published for Avast, AVG and Norton on 2026-09-04.
Because the fix is delivered as a driver replacement rather than a product version increment, administrators who need to confirm remediation should verify that the running sandbox driver (aswSnx.sys on Avast, avgSnx.sys on AVG, nllSnx.sys on Norton) is at or above the fixed version after the restart, rather than checking the product version.
Installations on release lines earlier than 26.7 do not receive these micro-updates and remain affected.
"}],"value":"Gen Digital has released a fix as an automatic micro-update to the sandbox driver. No product upgrade or reinstallation is required, and the product version number does not change.\n\n\n\nBecause the fix replaces a kernel-mode driver, a device restart is required to load it. Until the device is restarted the previous driver stays active and the system remains vulnerable. The application notifies the user to restart.\n\n * 26.7 release line: fixed driver version 26.7.1021.0\n * 26.8 release line: fixed driver version 26.8.1020.0\n\n\n\n\nThe update was published for Avast, AVG and Norton on 2026-09-04.\n\n\n\nBecause the fix is delivered as a driver replacement rather than a product version increment, administrators who need to confirm remediation should verify that the running sandbox driver (aswSnx.sys on Avast, avgSnx.sys on AVG, nllSnx.sys on Norton) is at or above the fixed version after the restart, rather than checking the product version.\n\n\n\nInstallations on release lines earlier than 26.7 do not receive these micro-updates and remain affected."}],"source":{"discovery":"EXTERNAL"},"title":"Avast sandbox privilege escalation via unpreserved DACLs on virtualized files in aswSnx.sys","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"Applying the driver micro-update described under Solution is the only complete remediation.
Where that update cannot be applied, Gen Digital ships detection for exploitation attempts against this issue, so keeping product virus definitions current provides detection of the publicly released proof-of-concept. Detection of a known proof-of-concept is not equivalent to the code fix and does not prevent variants.
Where the sandbox feature is not required, disabling it removes exposure to this attack path.
"}],"value":"Applying the driver micro-update described under Solution is the only complete remediation.\n\n\n\nWhere that update cannot be applied, Gen Digital ships detection for exploitation attempts against this issue, so keeping product virus definitions current provides detection of the publicly released proof-of-concept. Detection of a known proof-of-concept is not equivalent to the code fix and does not prevent variants.\n\n\n\nWhere the sandbox feature is not required, disabling it removes exposure to this attack path."}],"x_generator":{"engine":"Vulnogram 1.0.5"}}},"cveMetadata":{"assignerOrgId":"dbd8429d-f261-4b1e-94cc-ae3132817e2e","assignerShortName":"GEN","cveId":"CVE-2026-82964","datePublished":"2026-09-16T14:01:47.369Z","dateReserved":"2026-08-31T13:57:13.454Z","dateUpdated":"2026-09-17T18:42:28.924Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-16 15:17:55","lastModifiedDate":"2026-09-17 19:17:05","problem_types":["CWE-281","CWE-653","CWE-862","CWE-281 CWE-281: Improper Preservation of Permissions","CWE-653 CWE-653: Improper Isolation or Compartmentalization","CWE-862 CWE-862: Missing Authorization"],"metrics":{"cvssMetricV31":[{"source":"security@nortonlifelock.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":2,"impactScore":6}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-09-17T18:41:32.262077Z","id":"CVE-2026-82964","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"82964","Ordinal":"1","Title":"Avast sandbox privilege escalation via unpreserved DACLs on virt","CVE":"CVE-2026-82964","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"82964","Ordinal":"1","NoteData":"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.\n\n\n\nWhen 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.\n\n\n\nThe 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.","Type":"Description","Title":"Avast sandbox privilege escalation via unpreserved DACLs on virt"}]}}}