CVE-2025-7004
Description
Heap buffer overflow in Avast/AVG/Norton Antivirus PE scanning allows local code execution or denial-of-service via malformed files before VPS 25040308.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Heap buffer overflow in Avast/AVG/Norton Antivirus PE scanning allows local code execution or denial-of-service via malformed files before VPS 25040308.
Vulnerability
A heap buffer out-of-bounds write vulnerability exists in the virus scanning engine used by Avast Antivirus, AVG Antivirus, Norton Antivirus, Avast One, and Avast Business Antivirus on Windows, macOS, and Linux. The flaw is triggered when the scanner processes a malformed Windows PE file. Affected virus definition builds are those before VPS 25040308.
Exploitation
An attacker with local access or the ability to deliver a malformed PE file (e.g., via email, download, or removable media) can exploit this vulnerability. No authentication is required; the overflow occurs automatically when the antivirus scans the malicious file. The malformed PE file causes a heap buffer write beyond allocated bounds during parsing.
Impact
Successful exploitation can lead to arbitrary code execution with the privileges of the antivirus process, typically SYSTEM, resulting in full system compromise. Alternatively, the attacker could cause a denial-of-service by crashing the scanning process.
Mitigation
The vulnerability is fixed in virus definition build VPS 25040308. Users should ensure their antivirus definitions are updated to this version or later. Updates are delivered automatically through the Gen Digital update channel. No workaround is necessary as long as definitions are current.
Reference: [1]
AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: < VPS 25040308
- Range: < VPS 25040308
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.