# CVE-2025-10905: Collision in minifilter driver of Avast Free Antivirus results in disabling of real-time protection

> A local attacker with administrative privileges can disable real-time protection and self-defense mechanisms in Avast Free Antivirus.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-7rvm-5hwf-93cv

## What is CVE-2025-10905?

CVE-2025-10905 is a medium-severity vulnerability in Avast Free Antivirus, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Collision in MiniFilter driver in Avast Software Avast Free Antivirus  before 25.9  on Windows allows a local attacker with administrative privileges to disable real-time protection and self-defense mechanisms.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-10905?


## How do I fix CVE-2025-10905?

No fix has been published for CVE-2025-10905 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10905 being exploited?

There is no known exploitation of CVE-2025-10905 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10905 and fix it if it is affected.

What it is: CVE-2025-10905 is a medium-severity vulnerability in Avast Free Antivirus, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10905 in the wild and no public exploit code.

Affected product: Avast Free Antivirus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10905/ (Markdown: https://insights.sbomify.com/CVE-2025-10905/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10905
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10905
- OSV: https://osv.dev/vulnerability/CVE-2025-10905

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10905/
Summaries are generated and may contain mistakes; the official description above is the record.