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

CVE-2025-7002

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 Avira Antivirus engine when scanning a malformed PDF file may allow Local Execution of Code or Denial-of-Service of the antivirus engine process. This issue affects Avira Antivirus on Windows, macOS, and Linux for engine builds before 8.3.70.68.

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 Avira Antivirus engine when scanning malformed PDF files, allowing local code execution or denial of service of the antivirus process. Affects engine builds before 8.3.70.68 on Windows, macOS, and Linux.

MitigationUpdate Avira Antivirus engine to version 8.3.70.68 or later across all affected platforms.

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. Verify Avira Antivirus is installed
    Check for Avira presence via installed programs list, running processes, or service entries. On Windows, check Add/Remove Programs or registry. On macOS, check /Applications or System Preferences. On Linux, check package manager listings (dpkg, rpm, or yum).
    Affected if Avira Antivirus is present on the system
  2. Locate the Avira engine component
    Identify the Avira engine service or scanning component. On Windows, look for Avira GmbH services or the AVIRA engine process. On macOS and Linux, locate the avguard or scan engine daemon/process.
    Affected if Avira engine component is found running or installed
  3. Determine the installed engine version
    Query the engine version through available interfaces: command line (avconnutil, avpgldr, or similar engine utilities if available), the product's about dialog, or system information panels. If command line tools are unavailable, check version information in the Avira installation directory or package metadata.
    Affected if Version cannot be determined or is below 8.3.70.68
  4. Compare version against affected range
    Compare the identified engine build number to the vulnerable threshold: versions before 8.3.70.68 are affected. Any build number 8.3.70.68 or higher is not vulnerable to this specific issue.
    Affected if Installed version is below 8.3.70.68

The environment is affected if Avira Antivirus with an engine build version before 8.3.70.68 is installed and the PDF scanning feature is enabled, as the vulnerability triggers during malformed PDF file processing.

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 Avira Antivirus engine to version 8.3.70.68 or later across all affected platforms.

Recommended fix High confidence

Avira Antivirus engine version 8.3.70.68 or later

  1. 1. Open the Avira Antivirus application on the affected system (Windows, macOS, or Linux)
  2. 2. Navigate to the update or settings section within the Avira interface
  3. 3. Check the current engine version to confirm it is running a build before 8.3.70.68
  4. 4. Initiate a manual update or allow automatic updates to proceed
  5. 5. Verify the engine version has been updated to 8.3.70.68 or later after the update completes
  6. 6. Confirm the antivirus engine is functioning properly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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