dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-7019

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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
Stack overflow vulnerability in Avast Antivirus when scanning a malformed Office Open XML file may allow 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 25020100. 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

A stack overflow vulnerability exists in the antivirus scanning engine when parsing malformed Office Open XML files. The vulnerability is triggered during routine file scanning and can crash the antivirus process, causing denial of service. The vulnerable code is in the shared scanning logic delivered through Gen Digital's virus definition stream.

MitigationUpdate virus definitions to build VPS 25020100 or later. This is typically achieved through normal antivirus auto-update mechanisms; ensure automatic updates are enabled and verify the installed definition version meets the minimum threshold.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Gen Digital antivirus product
    Check installed programs for Norton, Avast, AVG, or other Gen Digital owned security products. This can be done via Control Panel > Programs and Features, or by running 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' in PowerShell.
    Affected if A Gen Digital antivirus product is installed (Norton, Avast, AVG, or related brand)
  2. Locate virus definition version
    Open the antivirus interface and navigate to the About, Support, or Settings section to find the virus definition or VPS version. For command-line access, common paths include scanning the process memory or checking product-specific logs in %ProgramData% or %AppData% folders.
    Affected if A VPS version number is displayed
  3. Compare VPS version to threshold
    Compare the installed VPS build number to the affected threshold of 25020100. Note that version formats may vary by product (some show as date codes like 2502-10-0, others as incremental numbers).
    Affected if VPS version is below 25020100 (or its date equivalent is earlier than 2025-02-01)
  4. Confirm Office file scanning is enabled
    Verify that real-time or on-demand scanning is enabled for Office documents. Check antivirus settings under 'File System Shield', 'Real-Time Protection', or 'Scan Settings' to ensure Office Open XML file types (.docx, .xlsx, .pptx) are included in scanning targets.
    Affected if Antivirus scanning of Office documents is enabled

A user is affected if they have a Gen Digital antivirus product with a virus definition version lower than VPS 25020100 and have Office file scanning 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 25020100 or later. This is typically achieved through normal antivirus auto-update mechanisms; ensure automatic updates are enabled and verify the installed definition version meets the minimum threshold.

Recommended fix High confidence

VPS 25020100 virus definitions (or higher)

  1. Ensure real-time protection is enabled and allow the antivirus to connect to update servers
  2. Trigger a manual virus definition update through the antivirus UI or command line
  3. Verify the updated virus definition build is VPS 25020100 or higher
  4. Confirm the antivirus process remains stable after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 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-7019 — 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-7019 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