- The Mess: Security researcher Chaotic Eclipse has released a public proof-of-concept called PrettyPrague targeting an alleged zero-day in Avast Antivirus. The researcher claims the Avast Sandbox can be abused to access Windows’ SAM database and spawn a shell as NT AUTHORITY\SYSTEM.
There is an important caveat.
This is currently a claimed vulnerability, not a vendor-confirmed CVE.
No CVE has been assigned.
No official Avast security advisory confirming the flaw has been published.
And there is no confirmed evidence that attackers are exploiting it in the wild.
But the PoC is public.
That changes the risk calculation.
PrettyPrague targets the Avast Sandbox, a privileged component designed to isolate suspicious activity.
According to Chaotic Eclipse, the exploit abuses that security boundary to reach the Windows Security Account Manager database — the SAM hive containing local account credential information — and then obtain SYSTEM-level command execution.
SYSTEM is the highest-privileged security context on Windows.
If the claim holds up, an attacker who already has code execution with lower privileges could use the flaw to break out of that boundary and take full control of the machine.
That’s the classic local privilege-escalation nightmare.
Except the vulnerable component is supposed to be part of the defense.
- The Damage: A working local privilege-escalation exploit against an antivirus product could let malware turn limited access into full SYSTEM control and potentially interfere with endpoint defenses.
The public PoC reportedly targets fully patched Windows 11 25H2 systems with Avast installed.
That detail matters.
This isn’t being presented as an attack against some abandoned Windows build.
The researcher claims the exploit works despite the operating system being fully updated.
However, the broader claim that every Avast version is vulnerable has not been independently verified.
The same applies to speculation that other Gen Digital products such as AVG or Norton may be affected.
For now, those claims should remain exactly that: claims.
What is confirmed is that PrettyPrague exists as publicly accessible exploit code.
The repository contains Windows-focused C/C++ components and a compiled x64 release.
The stated objective is to access the SAM database and launch a SYSTEM shell.
That gives other researchers — and potentially attackers — something concrete to analyze.
A public PoC also removes one of the most expensive parts of vulnerability research.
The initial discovery work has already been done.
An attacker doesn’t necessarily need to understand the entire vulnerability immediately.
They can start with the PoC, reverse-engineer the interesting parts and test whether the technique works against their own targets.
That’s why local privilege escalation bugs in security software deserve attention even when there is no remote attack.
A low-privileged foothold is often only the first step of an intrusion.
Once attackers reach SYSTEM, the rules change.
They can access protected operating-system resources, tamper with security controls, install persistence and attempt to extract credentials.
- The Fix: There is currently no confirmed Avast patch or official mitigation for PrettyPrague, so organizations should monitor Gen Digital’s security advisories, keep Avast fully updated and increase endpoint monitoring for suspicious privilege escalation and SAM access.
Do not disable Avast protection simply because a public PoC exists.
Avast itself warns that disabling its shields leaves systems exposed to attacks.
Instead, defenders should watch for unusual behavior around Avast processes and services.
Particular attention should go to suspicious processes that:
- access the SAM registry hive unexpectedly;
- spawn command interpreters from Avast-related processes;
- transition from a low-privileged user context to SYSTEM;
- perform unusual registry operations;
- modify or stop security software;
- create new privileged persistence mechanisms.
Endpoint telemetry is especially important while the technical details remain unsettled.
Security teams should also record the installed Avast build and maintain a clean timeline of endpoint activity.
If Gen Digital publishes a security advisory, administrators will need to map the affected versions quickly.
For now, the most sensible posture is simple:
Don’t panic. Don’t ignore it. Monitor it.
And don’t confuse “no confirmed exploitation” with “no risk.”
The PoC is already public.
Bugstoday Opinion
This is exactly the kind of vulnerability that makes security people uncomfortable.
An antivirus product has to run deep inside Windows.
It needs privileges.
It needs access to files.
It needs hooks into system activity.
It needs to see things normal applications aren’t supposed to see.
That makes security software incredibly powerful.
It also makes security software an attractive target.
If PrettyPrague’s claims survive independent validation, the attacker doesn’t have to defeat Windows directly.
They can attack the software that sits between Windows and the attacker.
And the most interesting part isn’t even the SAM access.
It’s the SYSTEM shell.
Because once a local attacker reaches SYSTEM, the antivirus isn’t protecting the machine anymore.
It has become the escalation mechanism.
Right now, the evidence needs to catch up with the headline.
There is no confirmed CVE.
There is no confirmed active exploitation.
There is no confirmed vendor acknowledgement.
But there is public exploit code.
That’s enough reason for defenders to start watching.
Your antivirus shouldn’t be the shortest path to SYSTEM.
Today’s Bugs. Tomorrow’s Breaches.
Technical Sources
Chaotic Eclipse / MSNightmare — PrettyPrague Public Proof-of-Concept
Cyber Security News — Chaotic Eclipse Claims Avast Antivirus 0-Day Vulnerability — PoC Released
Avast Support — Temporarily Disabling Avast Antivirus Protection
