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

CVE-2025-7009

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 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 Avast/AVG/Norton antivirus scanning engine when parsing malformed Windows PE files. The flaw exists in the shared Gen Digital virus definition scanning logic and can be triggered during routine file scanning, potentially allowing local code execution or denial-of-service of the antivirus process.

MitigationUpdate antivirus virus definitions to build VPS 25021310 or later across all affected endpoints (Windows, macOS, Linux). This is a standard virus definition update - no additional configuration or code changes required.

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. Confirm affected antivirus product is installed
    Check for Avast, AVG, or Norton antivirus software on the system by reviewing installed programs or running 'Get-ItemProperty' in PowerShell for registry entries under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or using the product's built-in about/help menu
    Affected if Any of these three products (Avast, AVG, or Norton) is installed on the system
  2. Locate the virus definition (VPS) build number
    Open the antivirus program UI and navigate to Settings > About, or right-click the system tray icon and select 'About' or 'Version information'. For command-line, use the product's CLI tool (e.g., 'avast --vps' or equivalent) or check the program's log files for the VPS/build version entry
    Affected if The VPS build number cannot be located or the product does not report VPS versions
  3. Compare installed VPS version to the fixed build
    Identify the VPS (Virus Protection Signature) build number reported in the previous step and compare it numerically to the fixed version 25021310. Note that older versions report builds in different formats (e.g., 25021201 for Feb 12, 2025)
    Affected if The installed VPS build number is lower than 25021310 (for example, 25021201 or earlier dates)
  4. Verify scanning engine processes Windows PE files
    Confirm the antivirus real-time or on-demand scanning is enabled and configured to scan executable files. Check if file type filtering includes .exe, .dll, .sys, or other PE file extensions. This is typically enabled by default in all three products
    Affected if File scanning for Windows executables is disabled or restricted to only non-PE file types

The environment is affected if Avast, AVG, or Norton is installed with a virus definition (VPS) build lower than 25021310, and the antivirus is configured to scan Windows PE files (the default configuration).

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 antivirus virus definitions to build VPS 25021310 or later across all affected endpoints (Windows, macOS, Linux). This is a standard virus definition update - no additional configuration or code changes required.

Recommended fix High confidence

VPS 25021310 or later (virus definition build)

  1. Ensure automatic virus definition updates are enabled in your Avast/AVG/Norton Antivirus settings
  2. Manually trigger a virus definition update to ensure you receive the latest definitions (VPS 25021310 or later)
  3. Verify the update was successful by checking the virus definition version - confirm it shows VPS 25021310 or higher
  4. For business environments, ensure the Central Management or admin console is configured to pull the latest virus definition stream

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-7009 — 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-7009 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