CVE-2025-0286
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 · uneditedVarious Paragon Software products contain an arbitrary kernel memory write vulnerability within biontdrv.sys that is caused by a failure to properly validate the length of user supplied data, which can allow an attacker to execute arbitrary code on the victim machine.
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 · moderate confidenceParagon Software's biontdrv.sys kernel driver fails to validate the length of user-supplied data before writing to kernel memory, allowing an attacker to write arbitrary data to kernel memory and execute code with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 15, <= 17.39>= 15, <= 16>= 15, <= 16>= 15, <= 17.39>= 4, <= 5>= 15, <= 17.39CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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.
-
Locate the biontdrv.sys driver fileSearch for biontdrv.sys in the Windows\System32\drivers folder and in Paragon program directories (typically C:\Program Files\Paragon Software\ or C:\Program Files (x86)\Paragon Software\)Affected if The driver file exists on the system, indicating the vulnerable component is present
-
Check the biontdrv.sys file versionRight-click the biontdrv.sys file, select Properties, and view the Details tab to obtain the File Version. Alternatively, run `driverquery /v /fo list | findstr biontdrv` or use PowerShell `Get-ItemProperty` on the driver fileAffected if The file version falls within or above version 15.0.0.0 and is less than or equal to 17.39.x.x (for Disk Wiper/Drive Copy, less than or equal to 16.x.x) - compare your version against the affected ranges for your specific product
-
Identify installed Paragon Software productsOpen Programs and Features (appwiz.cpl) or check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries starting with 'Paragon'Affected if Any Paragon product from the affected list is installed: Backup & Recovery, Disk Wiper, Drive Copy, Hard Disk Manager, Migrate Os To Ssd, or Partition Manager
-
Verify the driver is loaded or loadableOpen an elevated command prompt and run `sc query biontdrv` to check driver status, or view loaded drivers with `driverquery /v | findstr biontdrv`Affected if The driver is present as a service or loaded in memory, meaning the attack surface is active
You are affected if biontdrv.sys is present on your system AND its version matches the affected ranges for your installed Paragon product (versions 15 through the upper bound for your specific product).
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.
From vendor dataApply available vendor patches or updates for affected Paragon Software products to remediate the biontdrv.sys vulnerability; consider disabling the driver if not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0286 — 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-0286 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