CVE-2026-12786
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 · uneditedA vulnerability has been found in Ezbsystems UltraISO Premium Edition up to 9.76. Affected by this issue is some unknown functionality in the library bootpt64.sys of the component Kernel Driver. The manipulation leads to improper access controls. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceVulnerability in Ezbsystems UltraISO Premium Edition up to v9.76 affecting the bootpt64.sys kernel driver component. The issue involves improper access controls in the kernel driver, which could allow a local attacker to potentially escalate privileges or perform unauthorized kernel-level operations. Public exploit availability increases risk.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check if UltraISO is installedLook for UltraISO installation directory, typically in C:\Program Files\EZBSystems\UltraISO or C:\Program Files (x86)\EZBSystems\UltraISO. Also check Add/Remove Programs for UltraISO entry.Affected if UltraISO Premium Edition is installed on the system
-
Identify installed UltraISO versionOpen the installed UltraISO application and check Help > About, or locate the executable (usually isourafi.exe or ultraiso.exe) and view its file properties for version information.Affected if Version is 9.76 or lower (any version up to and including 9.76)
-
Locate the bootpt64.sys driver fileSearch for bootpt64.sys in the UltraISO installation folder and subdirectories. The driver is typically found in the driver or sys subfolder within the UltraISO program directory.Affected if The bootpt64.sys driver file exists in the UltraISO installation directory
-
Check if bootpt64.sys driver is loadedOpen Command Prompt as Administrator and run 'driverquery /v | findstr bootpt64' or check Device Manager for hidden devices. Also check HKLM\SYSTEM\CurrentControlSet\Services\bootpt64 in the registry.Affected if The bootpt64 driver is loaded or registered as a system service
-
Verify driver file versionRight-click bootpt64.sys and select Properties, then view the Version tab to see the file version. Compare against known vulnerable driver versions.Affected if Driver version corresponds to UltraISO 9.76 or earlier
A system is affected if UltraISO Premium Edition version 9.76 or lower is installed AND the bootpt64.sys kernel driver is present on the system.
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 dataUntil vendor patch is released, restrict or eliminate use of UltraISO on sensitive systems; if required, run with least privilege and monitor for suspicious driver loading. Consider alternative ISO mounting software that does not require kernel drivers.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12786 — 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-2026-12786 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