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

CVE-2025-7011

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 out-of-bounds read vulnerability in Avast Antivirus when scanning a malformed zip file containing XML 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 from 25020100 before 25021208. 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 out-of-bounds read vulnerability in Avast/AVG/Norton antivirus scanning engine when parsing malformed XML files within zip archives, potentially allowing local code execution or denial-of-service of the antivirus process.

MitigationUpdate virus definition builds to 25021208 or later via the Gen Digital update stream; all affected products (Avast, AVG, Norton, Avast One, Avast Business) receive the fix through this shared channel.

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 security product
    Check installed programs for Avast, AVG, Norton, Avast One, or Avast Business using 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' or the Programs and Features control panel
    Affected if Any of these products are installed and the engine/definition version is below 25021208
  2. Check antivirus engine or definition build version
    Open the antivirus UI and navigate to Settings > About, or right-click the system tray icon and select 'About'. Look for a build number, version, or engine version entry
    Affected if The displayed build or version number is lower than 25021208
  3. Verify XML scanning is enabled by default
    The vulnerability triggers during automated scanning of ZIP archives - confirm real-time or scheduled scanning is enabled in the product settings under Shields, Protection, or Scanning options
    Affected if Real-time file system monitoring or scheduled scans are active and the product version is vulnerable
  4. Confirm ZIP archive processing capability
    The vulnerability occurs when the engine parses XML files inside ZIP archives - verify archive scanning is enabled in the antivirus settings under 'Scanning' or 'Shields' options
    Affected if Archive scanning is enabled and the definition build is below 25021208

A user is affected if they have any Avast, AVG, Norton, Avast One, or Avast Business product installed with a virus definition or engine build number earlier than 25021208.

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 25021208 or later via the Gen Digital update stream; all affected products (Avast, AVG, Norton, Avast One, Avast Business) receive the fix through this shared channel.

Recommended fix High confidence

Virus definition build 25021208 or later (from the Gen Digital update stream)

  1. Open the Avast/AVG/Norton antivirus application on the affected system
  2. Navigate to Settings or Protection settings
  3. Locate the Virus Definitions or Updates section
  4. Check for and install any available updates
  5. Verify that the virus definition build is at or above 25021208 after the update completes

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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