CVE-2026-129255: Contain the Cooler Master MASTERPLUS+ driver flaw
If you have Cooler Master MASTERPLUS+ 1.9.6 installed, review whether you still need it and ask Cooler Master for a fix covering CVE-2026-129255. The VulDB CNA record identifies a local permissions flaw in its WinRing0x64.sys driver. It names no fixed release. Cooler Master’s MASTERPLUS+ page still lists 1.9.6 in its release notes, checked November 14, 2026.
What is affected
The CNA identifies MASTERPLUS+ 1.9.6, the driver’s sub_11504 function and its PhysicalAddress argument. It classifies the issue as incorrect default permissions and incorrect privilege assignment. The record does not establish an affected range for earlier or later releases, or for other products that use a driver with the same filename.
VulDB assigns CVSS 4.0 9.3 Critical and CVSS 3.1 8.8 High. Both vectors specify local access, low privileges and no user interaction. Keep the scoring version with the rating; the Critical label does not describe an unauthenticated network attack.
The CNA timeline dates advisory disclosure to November 13. The CVE record was published on November 14 at 12:30:17 UTC. VulDB’s advisory reports no available exploit or known mitigation. The reviewed sources do not establish active exploitation.
Contain exposure while a fix is unconfirmed
These are defensive recommendations, not a vendor-confirmed workaround:
- Check MASTERPLUS+’s installed version on Windows, using the application information or your approved software inventory. Record which computers have 1.9.6 and whether the associated driver is installed or loaded. A filename match alone cannot identify the vulnerable build.
- If you can retire MASTERPLUS+, use its supported uninstall process after checking which hardware features depend on it. Save relevant profiles and arrange a maintenance window. Do not manually delete a running driver or guess at service names. After the required restart, have the administrator verify that the driver is no longer loaded and that necessary hardware functions still work.
- If removal is impractical, restrict untrusted local software and interactive access while you seek a supported fix. A local, low-privilege attack remains relevant to a computer where malicious code already runs. Closing the application’s window is not evidence that its driver has unloaded.
Review Windows driver protections with the endpoint administrator. Microsoft’s recommended driver block rules explain the vulnerable driver blocklist and memory integrity. Microsoft warns that the list does not cover every vulnerable driver and that blocking can break software or devices. Do not assume that enabling it proves this particular MASTERPLUS+ driver is blocked. Test policy changes in audit mode and follow Microsoft’s deployment guidance before enforcement.
Ask the vendor for the corrected package version and driver identification, with an explicit reference to this CVE. Verify those details before reinstalling or restoring normal access. A generic bug-fix note or a newer download is insufficient evidence of remediation. If an organization supplies its own patched package, obtain its advisory and build identifier rather than judging by the upstream version alone.
This is a Windows application-driver issue. Linux distribution updates or backports do not repair the affected Windows installation.
Inspect the public record from Linux
The example below downloads advisory metadata only. It needs Bash, curl and Python 3, and neither connects to a Windows computer nor opens a driver. Create a scratch directory, and keep the same terminal session through cleanup. Stop if setup fails.
advisory_dir=$(mktemp -d ./masterplus-advisory.XXXXXX) &&
cd -- "$advisory_dir"Save this source as inspect-masterplus-record.py:
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
metadata = record["cveMetadata"]
if metadata["cveId"] != "CVE-2026-129255":
raise SystemExit("Expected CVE-2026-129255")
cna = record["containers"]["cna"]
print("CVE:", metadata["cveId"])
print("CNA:", metadata["assignerShortName"])
print("Published (UTC):", metadata["datePublished"])
for event in cna.get("timeline", []):
if event["value"] == "Advisory disclosed":
print("Advisory disclosure (CNA):", event["time"])
for product in cna["affected"]:
for version in product["versions"]:
if version["status"] == "affected":
print("Listed affected:", product["product"], version["version"])
for metric in cna.get("metrics", []):
for key in ("cvssV4_0", "cvssV3_1"):
if key in metric:
score = metric[key]
print("CVSS", score["version"], score["baseScore"], score["baseSeverity"])
print("Metadata only; no Windows device or driver was tested.")Download the record and run the helper:
curl --fail --silent --show-error --max-time 30 \
'https://cveawg.mitre.org/api/cve/CVE-2026-129255' \
--output masterplus-cve.json &&
python3 inspect-masterplus-record.py masterplus-cve.jsonActual output on Debian 13 with Python 3.12.14, November 14, 2026:
CVE: CVE-2026-129255
CNA: VulDB
Published (UTC): 2026-11-14T12:30:17.941Z
Advisory disclosure (CNA): 2026-11-13T00:00:00.000Z
Listed affected: MASTERPLUS+ 1.9.6
CVSS 4.0 9.3 CRITICAL
CVSS 3.1 8.8 HIGH
Metadata only; no Windows device or driver was tested.The helper checks the CVE identifier and prints the CNA’s fields. It does not determine whether your computer is vulnerable or patched. The downloaded record may change; retain a copy with its retrieval date if you need it for an incident ticket.
From the scratch directory in the same terminal session, optional cleanup removes only the two example files and their empty directory:
rm -- inspect-masterplus-record.py masterplus-cve.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dirSetup and cleanup completed without output. No Windows installation, exploit, uninstall procedure or driver-blocking policy was tested.
This post was created with assistance from AI.