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

CVE-2025-9033

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.76.

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's PDF scanning component when processing malformed PDF files. The vulnerability allows local code execution or DoS of the antivirus engine process via malicious PDF input.

MitigationUpdate Avira Antivirus engine to build 8.3.70.76 or later on all affected platforms (Windows, macOS, Linux).

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. Check Avira Antivirus engine version
    Open Avira user interface and navigate to Help > About, or check the installed version via system information. On Windows, also check the version property of the main Avira executable in Program Files. On macOS, check via Avira > About Avira. On Linux, run 'avupdate --version' or check the installed RPM/DEB package version.
    Affected if The installed engine version is lower than 8.3.70.76 (e.g., 8.3.70.75, 8.3.x earlier versions, or any version before 8.3.70.76).
  2. Verify real-time protection or file scanning is active
    Check Avira's main status screen or settings to confirm that real-time protection (often called 'Real-Time Protection' or 'Guard') is enabled, or that on-demand scanning is configured to scan PDF files.
    Affected if Scanning is enabled and the engine version is in the affected range before 8.3.70.76.
  3. Confirm PDF file scanning is not excluded
    Review Avira's scan profiles, exclusion settings, or file type filters to ensure PDF files are being scanned and not explicitly excluded from scanning.
    Affected if PDF files are set to be scanned (not excluded) and the engine version is vulnerable.
  4. Identify the Avira scanning engine process
    Check running processes during a scan or file access to identify the Avira scanning engine process (typically a component like 'avscan.exe', 'avguard.exe', or similar service process that handles file analysis).
    Affected if The scanning engine process is running and its version is before 8.3.70.76.

The environment is affected if the Avira Antivirus scanning engine version is lower than 8.3.70.76 and PDF file scanning is enabled or scheduled to run.

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 build 8.3.70.76 or later on all affected platforms (Windows, macOS, Linux).

Recommended fix High confidence

Avira Antivirus engine build 8.3.70.76 or later

  1. Identify current Avira Antivirus engine version by opening Avira and checking 'About' or 'Settings > Maintenance'
  2. Download and install the latest Avira Antivirus version from the official Avira website or through the application's built-in update feature
  3. Ensure the engine version is 8.3.70.76 or later after updating
  4. Verify the update was successful by re-checking the engine version in the application

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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