Skip to main content
Mallory
HighVulnerability

CVE-2022-26522: Kernel privilege escalation in Avast/AVG aswArPot.sys socket connection handler

Published May 8, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.18%8th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2022-26522CWE-367 · Time-of-check Time-of-use (TOCTOU)…
Also known asPrivilege Escalation via Avast Anti-Rootkit Driver (CVE-2022-26522)

CVE-2022-26522 is a local privilege escalation vulnerability in the Avast and AVG Windows Anti Rootkit driver aswArPot.sys before version 22.1. The flaw resides in the socket connection handler at aswArPot+0xc4a3 and is described as a double-fetch race condition involving PPEB->ProcessParameters->CommandLine.Length. The driver fetches a user-controlled length value more than once without ensuring it remains stable, allowing an attacker to race a kernel thread and modify the CommandLine.Length field between accesses. By triggering the vulnerable path via a socket connection, a local attacker can induce memory corruption in kernel context, leading to arbitrary code execution in kernel mode or a system crash.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow a non-administrative local attacker to escalate privileges to kernel/SYSTEM-equivalent execution. Because the bug is reachable in a security product kernel driver, exploitation can enable complete device takeover, including disabling security tools, overwriting system components, corrupting the operating system, and performing arbitrary actions without interference. Unsuccessful or partial exploitation can result in denial of service through memory corruption and OS crash.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by preventing untrusted local code execution, restricting user ability to run arbitrary programs, and monitoring for abuse of Avast/AVG kernel drivers in privilege-escalation chains. Defend against bring-your-own-vulnerable-driver techniques with application control, driver block rules, and EDR detections for suspicious loading or use of vulnerable security drivers. These are compensating controls only; the primary mitigation is updating to 22.1 or later.

Remediation

Patch, then assume compromise.

Upgrade Avast and AVG products to version 22.1 or later, which fixes CVE-2022-26522. Replace vulnerable copies of aswArPot.sys on affected systems by applying the vendor-provided product update. Ensure endpoints have received the updated driver version rather than relying solely on application-level version reporting.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2022-26522 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-26522?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2022-26522.
Is there a patch for CVE-2022-26522?
Upgrade Avast and AVG products to version 22.1 or later, which fixes CVE-2022-26522. Replace vulnerable copies of aswArPot.sys on affected systems by applying the vendor-provided product update.
How severe is CVE-2022-26522?
CVE-2022-26522 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.18% (8th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.