CVE-2025-14098
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 · uneditedHeap buffer out-of-bounds write vulnerability due to integer overflow in Avira Antivirus engine when scanning a malformed MS-DOS executable 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.104.
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 confidenceHeap buffer out-of-bounds write vulnerability caused by integer overflow in Avira Antivirus engine when parsing malformed MS-DOS executable files. This allows local code execution or denial-of-service of the antivirus engine process.
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 checksWork through these to decide whether this CVE applies to you.
-
Determine Avira engine versionOpen Avira main console, navigate to Help > About, or run 'avregistry.exe' / avscan -v from command line. On Windows check registry key HKLM\SOFTWARE\Avira\AviraFiltrer\Version. On macOS/Linux check /Library/Application Support/Avira/Version or /var/lib/avira/version file.Affected if version is below 8.3.70.104
-
Confirm real-time protection is enabledOpen Avira > Real-Time Protection status. On Windows check registry key HKLM\SYSTEM\CurrentControlSet\Services\AviraRealtimeMonitor\Start (value 2 or 3 means running). On macOS check System Preferences > Avira > Real-Time Protection.Affected if real-time scanning is active and engine version is vulnerable
-
Verify on-demand scanning capabilityCheck if file scanner module is loaded. Run 'avscan --info' or examine running processes for 'avguard.exe' or 'Avira.Spotlook.Service' processes.Affected if on-demand scanning processes are running and engine version is vulnerable
You are affected if Avira Antivirus engine version is below 8.3.70.104 and either real-time protection or on-demand file scanning is enabled, allowing the engine to scan malformed MS-DOS executable files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Avira Antivirus engine to version 8.3.70.104 or later across all affected platforms (Windows, macOS, Linux).
Avira Antivirus engine version 8.3.70.104 or later
- Open the Avira Antivirus application on your system
- Navigate to the Updates section or Help > Check for Updates
- Run the update process to download and install the latest engine version
- Confirm the engine version is 8.3.70.104 or later after updating
- Alternatively, download the latest Avira Antivirus installation package from the official Avira website and reinstall to ensure the updated engine
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14098 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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