dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-7008

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 read vulnerability in Avast Antivirus when scanning a malformed Windows PE file with .NET metadata 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 25021310. 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 read vulnerability in the Gen Digital antivirus scanning engine when parsing malformed Windows PE files containing .NET metadata. The vulnerability allows local code execution or denial-of-service of the antivirus process by triggering the flawed parsing logic during file scanning.

MitigationUpdate virus definitions to build VPS 25021310 or later across all affected Avast, AVG, Norton, and Avast Business installations to remediate the vulnerability.

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, or Avast Business. On Windows, use 'Programs and Features' or run: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName | Where DisplayName -match 'Avast|AVG|Norton'
    Affected if None of these four products are installed (Avast, AVG, Norton, Avast Business)
  2. Check virus definition (VPS) build version
    Open the antivirus interface and navigate to Settings > About, or right-click the system tray icon and select 'About'. Look for the VPS (Virus Protection Definitions) or virus signature database build number.
    Affected if The VPS/build version is earlier than 25021310 or cannot be determined (unpatched installations)
  3. Verify scanning engine is active
    Check that real-time file system protection or on-demand scanner is enabled. In the antivirus settings, confirm 'File Shield', 'Real-Time Protection', or equivalent scanning component is turned on.
    Affected if Real-time or on-demand scanning is disabled (the vulnerability only triggers during file scanning)
  4. Confirm Windows PE file scanning is enabled
    In antivirus settings, verify that scanning of executable files and PE files is not excluded or disabled. Look for settings related to 'Scan executables', 'Scan PE files', or 'File types to scan'.
    Affected if PE file scanning is disabled or .NET file types are excluded from scanning

You are affected if a Gen Digital product (Avast, AVG, Norton, or Avast Business) is installed with a VPS build version earlier than 25021310 and file scanning is enabled.

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 definitions to build VPS 25021310 or later across all affected Avast, AVG, Norton, and Avast Business installations to remediate the vulnerability.

Recommended fix High confidence

VPS 25021310 or higher virus definitions (delivered via Gen Digital update stream)

  1. Ensure automatic virus definition updates are enabled in your Avast/AVG/Norton/Avast One or Avast Business Antivirus product
  2. Manually trigger a virus definition update by opening the antivirus interface and selecting 'Update' or 'Check for updates'
  3. Verify the installed virus definition (VPS) version is 25021310 or higher to confirm the vulnerability is mitigated
  4. For Enterprise/Business deployments, ensure the central management console is distributing virus definition builds >= VPS 25021310

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7008 — 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-7008 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