CVE-2026-12193
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 was identified in VS Revo RevoUninstaller 2.5.x/2.6.x. The affected element is the function IOCtl_Handler in the library RevoDetector.sys of the component IOCTL Handler. Such manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit is publicly available and might be used. Upgrading to version 2.7.0 is sufficient to fix this issue. It is recommended to upgrade the affected component.
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-based buffer overflow in the IOCtl_Handler function of RevoDetector.sys kernel driver in VS Revo RevoUninstaller versions 2.5.x/2.6.x allows local privilege escalation via malicious IOCTL requests.
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.
-
Find installed Revo Uninstaller versionOpen Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed software. Locate Revo Uninstaller and note its version number.Affected if The version starts with 2.5.x or 2.6.x (for example, 2.5.0 through 2.5.9, or 2.6.0 through 2.6.9)
-
Locate RevoDetector.sys driver fileSearch for RevoDetector.sys in the Revo Uninstaller installation directory (commonly C:\Program Files\Revo Uninstaller or C:\Program Files (x86)\Revo Uninstaller). Verify the file exists.Affected if The file RevoDetector.sys exists in the Revo Uninstaller installation folder, indicating the vulnerable driver is present.
-
Check if driver is loadedOpen Command Prompt as Administrator and run 'sc query RevoDetector' or view loaded drivers with 'driverquery /v | findstr RevoDetector' to check driver status.Affected if The driver shows as RUNNING or LOADED, meaning the vulnerable IOCTL handler is active and the attack surface is exposed.
-
Compare version to affected rangesCross-reference the installed Revo Uninstaller version with the affected versions 2.5.x and 2.6.x. If the version falls within these ranges, the vulnerability is present.Affected if Installed version is 2.5.x or 2.6.x, confirming the environment contains the unpatched driver.
A user is affected if Revo Uninstaller version 2.5.x or 2.6.x is installed with the RevoDetector.sys driver present and loaded 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.
dbcve · scopedUpgrade to version 2.7.0 which contains the vendor fix for this kernel driver buffer overflow vulnerability.
Revo Uninstaller 2.7.0
- Download Revo Uninstaller version 2.7.0 from the official vendor website
- Uninstall the current version (2.5.x or 2.6.x)
- Install version 2.7.0 which contains the fixed RevoDetector.sys driver
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12193 — 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-12193 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