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

CVE-2025-10101

HIGH · 7.8 CVSS v3.1 Published 2025-12-01
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 Mach-O 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 25090300. 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 antivirus scanning engine when parsing malformed Mach-O (Apple executable) files. This memory safety issue in the file scanning logic could allow an attacker to achieve local code execution or cause denial-of-service of the antivirus process by tricking a user into scanning a specially crafted file.

MitigationUpdate virus definitions to build VPS 25090300 or later through the standard Gen Digital update stream; installations at or above this build are not vulnerable regardless of which affected product is used.

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 Gen Digital antivirus is present
    Check installed programs or running processes for Norton, Avast, AVG, or other Gen Digital antivirus products
    Affected if No Gen Digital antivirus product is installed on the system
  2. Locate virus definition database
    Find the virus pattern file in the antivirus program directory (commonly named virusdefs.dat, vps*.dat, or similar)
    Affected if Cannot locate the virus definition database file
  3. Read VPS build version
    Open the virus definition file properties or check the antivirus product UI for the VPS (Virus Protection Signature) build number
    Affected if Cannot determine the VPS build version from the definition file or product interface
  4. Compare to fixed build
    Compare the installed VPS build number to the fixed version 25090300; versions below this threshold are vulnerable
    Affected if Installed VPS build number is lower than 25090300

Environment is affected if a Gen Digital antivirus product is present with virus definitions (VPS build) below 25090300.

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 25090300 or later through the standard Gen Digital update stream; installations at or above this build are not vulnerable regardless of which affected product is used.

Recommended fix High confidence

Virus definition build VPS 25090300 or later

  1. Open your Avast, AVG, Norton, Avast One, or Avast Business Antivirus application
  2. Navigate to the virus definition update or settings section
  3. Initiate a manual update of the virus definitions
  4. Verify that the updated virus definition build is VPS 25090300 or higher
  5. Ensure automatic updates are enabled to maintain protection against future threats

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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