Skip to content
CVE-2026-129261: Contain the Kingston FURY CTRL driver flaw

CVE-2026-129261: Contain the Kingston FURY CTRL driver flaw

November 14, 2026

Check Windows machines running Kingston FURY CTRL RGB Control Software through version 2.0.66.0. CVE-2026-129261 concerns insufficient access control in the NTIOLib_X64.sys driver’s IOCTL handling. The CNA record lists no fixed version. If the RGB utility is unnecessary, plan its removal with the endpoint administrator and verify that the affected driver can no longer load.

Scope and severity

VulDB, the assigning CNA, rates the flaw 9.3 Critical under CVSS 4.0, but 8.2 High under CVSS 3.1 and 3.0. The CVSS 4.0 and 3.1 vectors specify local access, high privileges and no user interaction. Treat it as a privileged local driver issue; the record does not describe an unauthenticated network attack.

The CNA dates advisory disclosure to November 13, 2026. The CVE record was published on November 14 at 16:00:15 UTC. VulDB’s advisory also gives November 13 as the disclosure date and lists no known mitigation. Its earlier community-submission date is not proof of when the report became public. The reviewed sources do not establish exploitation in the wild.

Kingston distributes FURY CTRL as Windows software for RGB lighting. This advisory concerns its software driver, not a demonstrated defect in the memory modules themselves. Installing Linux distribution updates on another machine will not fix the Windows installation.

Reduce exposure while seeking a confirmed fix

Record the FURY CTRL application version from the installed application or your endpoint inventory. Include affected test benches and gaming workstations in the search. Ask the endpoint administrator to check the installed and loaded driver inventory for NTIOLib_X64.sys; a filename alone does not establish its version, origin or remediation status.

For machines that do not need the utility, use the supported uninstall process and schedule a reboot if required. Then verify that the affected driver is no longer loaded and cannot reload through a remaining service or another installation. Closing the RGB window is not sufficient evidence. Do not manually delete driver files or disable arbitrary services on a working machine.

Keep administrator access limited to trusted accounts. Review unexpected driver installations and endpoint-security alerts. These are containment recommendations, not a vendor-confirmed workaround or evidence that an endpoint was compromised.

Microsoft’s vulnerable-driver blocklist guidance describes another defense, but Microsoft explicitly warns that the list does not cover every vulnerable driver. This article has not verified a matching block for the affected Kingston binary. Test driver-control policy changes before enforcement because blocking a needed driver can break devices or cause a blue screen. The ASR rule that prevents vulnerable drivers being written to disk does not stop an existing driver from loading.

Require evidence before reinstalling

Ask Kingston support for a release or supported remediation that explicitly addresses CVE-2026-129261. Neither the CNA record nor the reviewed Kingston product page identifies a fixed release as of November 14, 2026. Do not assume an installer is safe merely because it is the latest download or has a higher version number.

For an OEM-supplied or repackaged installation, obtain confirmation for that exact package. A backported fix may retain an older-looking version, so retain the vendor’s advisory and package evidence. After remediation, verify the driver state following a reboot and test required hardware functions. No Kingston installation, uninstaller or Windows mitigation was tested for this article.

Inspect the public record from Linux

This example reads public CVE metadata. It does not load a driver, send IOCTLs or test a Windows endpoint. It needs Bash, curl and Python 3. Keep the same terminal session for cleanup, and stop if creating or entering the scratch directory fails.

advisory_dir=$(mktemp -d ./kingston-advisory.XXXXXX) &&
cd -- "$advisory_dir"

Save this source as inspect-kingston-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-129261":
    raise SystemExit("Expected CVE-2026-129261")

cna = record["containers"]["cna"]
print(f"CVE: {metadata['cveId']}")
print(f"Record published: {metadata['datePublished']}")
for event in cna.get("timeline", []):
    if event["value"] == "Advisory disclosed":
        print(f"CNA disclosure date: {event['time'][:10]}")
for metric in cna["metrics"]:
    for key in ("cvssV4_0", "cvssV3_1"):
        if key in metric:
            score = metric[key]
            print(f"CVSS {score['version']}: "
                  f"{score['baseScore']} {score['baseSeverity']}")
            print(f"  {score['vectorString']}")
for product in cna["affected"]:
    print(f"Product: {product['vendor']} {product['product']}")
    versions = product.get("versions", [])
    print("2.0.66.0 marked affected: " + str(any(
        v.get("version") == "2.0.66.0" and v["status"] == "affected"
        for v in versions
    )))
    print("Unaffected version entries: " + str(sum(
        v["status"] == "unaffected" for v in versions
    )))

Download the record, then run the script only if the download succeeds:

curl --fail --silent --show-error --location --max-time 60 \
  'https://cveawg.mitre.org/api/cve/CVE-2026-129261' \
  --output kingston-cve.json &&
python3 inspect-kingston-record.py kingston-cve.json

Actual output on Linux x86_64 with Python 3.12.14 and curl 8.14.1, November 14, 2026:

CVE: CVE-2026-129261
Record published: 2026-11-14T16:00:15.614Z
CNA disclosure date: 2026-11-13
CVSS 4.0: 9.3 CRITICAL
  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
CVSS 3.1: 8.2 HIGH
  CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:X/RL:X/RC:R
Product: Kingston FURY CTRL RGB Control Software
2.0.66.0 marked affected: True
Unaffected version entries: 0

Zero unaffected entries means the record does not enumerate a safe version. It does not prove that no fix exists elsewhere. Recheck the live record and Kingston’s guidance before making a remediation decision.

Remove only the two example files, then remove the scratch directory if it is empty:

rm -- inspect-kingston-record.py kingston-cve.json
cd .. && rmdir -- "$advisory_dir"

Acknowledgment

This article was prepared with AI assistance. The public-record example was executed on Linux; the vulnerability was not reproduced, and no third-party system was probed.

Last updated on