dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-7004

HIGH · 7.8 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap buffer out-of-bounds write vulnerability in Avast Antivirus when scanning a malformed Windows PE file may allow Local Execution of Code or Denial-of-Service of the antivirus process. This issue affects Avast Antivirus, AVG Antivirus, Norton Antivirus, Avast One, and Avast Business Antivirus on Windows, macOS, and Linux for virus definition builds before VPS 25040308. The affected scanning logic is delivered through a shared Gen Digital virus definition update stream. The same stream feeds the consumer antivirus products listed in this advisory and other Gen Digital products that embed the same engine. Mitigation flows through this update channel; installations at or above the listed build are not vulnerable regardless of which product consumes the stream.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap buffer out-of-bounds write vulnerability in the Gen Digital antivirus scanning engine when parsing malformed Windows PE files. The vulnerability exists in the virus definition scanning logic and can be triggered during routine file scanning, potentially allowing local code execution or causing the antivirus process to crash.

MitigationUpdate virus definition builds to VPS 25040308 or later across all affected products (Avast, AVG, Norton, Avast One, Avast Business Antivirus) on Windows, macOS, and Linux. This is delivered through the standard Gen Digital virus definition update stream.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Gen Digital product
    Check installed programs for Avast, AVG, Norton, Avast One, or Avast Business Antivirus. On Windows: Control Panel > Programs and Features or Settings > Apps. On macOS: Applications folder. On Linux: dpkg -l or rpm -qa for respective packages.
    Affected if Any of these Gen Digital products are installed on the system
  2. Check virus definition (VPS) version
    Open the antivirus interface and navigate to Settings > About or Help > About, then locate the Virus Definitions or VPS version number. Alternatively, on Windows command line: C:\Program Files\Avast Software\Avast\avastuwus.exe /VPS (path varies by product). On Linux: /opt/avg/bin/avgctl -g or equivalent. On macOS: Right-click app > Show Package Contents > Contents/Resources/version.txt or check within Preferences.
    Affected if The displayed VPS version is below 25040308 or the version cannot be determined (indicating outdated definitions)
  3. Verify scanning engine is active
    Confirm real-time or on-demand file scanning is enabled. Check antivirus settings for 'File Shield', 'Real-Time Protection', or 'Smart Scan' status. The vulnerability triggers during PE file parsing in the scanning engine.
    Affected if File scanning is enabled (this is default behavior) and VPS version is below 25040308
  4. Confirm Windows PE file scanning capability
    The vulnerability affects parsing of Windows PE files. Verify the antivirus is configured to scan executable files. Check that file type scanning includes .exe, .dll, .sys. This is typically enabled by default in all Gen Digital products.
    Affected if PE file scanning is active (default setting) and VPS version is below 25040308

A system is affected if any Gen Digital product (Avast, AVG, Norton, Avast One, Avast Business Antivirus) is installed with a virus definition (VPS) version earlier than 25040308, with file scanning enabled to process Windows PE files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update virus definition builds to VPS 25040308 or later across all affected products (Avast, AVG, Norton, Avast One, Avast Business Antivirus) on Windows, macOS, and Linux. This is delivered through the standard Gen Digital virus definition update stream.

Recommended fix High confidence

VPS 25040308 (virus definition build)

  1. Open your Avast/AVG/Norton antivirus application
  2. Navigate to the virus definition or update settings
  3. Ensure virus definitions are updated to VPS 25040308 or later
  4. Verify the update completed successfully
  5. For enterprise deployments, ensure the virus definition stream is configured to receive updates and confirm the VPS version meets or exceeds 25040308

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7004 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data