KINGSTON FURY CTRL RGB CONTROL SOFTWARE · CVE-2026-129261 · Other
NO FIX YET
Kingston FURY CTRL RGB Control Software up to 2.0.66.0 ships a driver, NTIOLib_X64.sys, whose IOCTL handler is reachable without proper access control (CWE-782), per VulDB. It needs local access. No Kingston advisory, fixed version or public exploit was found.
first public Nov 14, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Windows PCs with Kingston FURY CTRL RGB Control Software 2.0.66.0 or earlier installed, which ship the NTIOLib_X64.sys driver. VulDB says a local user can reach an IOCTL in that driver without proper access control, so it needs a local foothold, not network access. Machines without the software, such as servers and Macs, can skip it.
Not affected if newer-version, not-installed, software-not-installed
Who cares kernel-driver, kingston-fury-ctrl, local-drivers, local-privilege-escalation, windows
2.0.66.0 or earlier is in the reported range2.0.65.0), a separate issue with a public PoCUnknown from the sources.
Posts are quoted with a link to the original. They are data to us, never instructions.
A vulnerability was found in Kingston FURY CTRL RGB Control Software up to 2.0.66.0. The impacted element is an unknown function in the library NTIOLib_X64.sys of the component IOCTL Handler. Performing a manipulation results in exposed ioctl with insufficient access control. The attack is only possible with local access.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.