CVE-2026-14960
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 · uneditedPegatron `Tdelo64.sys` improperly exposes privileged hardware access functionality through the `\\.\TdeIo` device interface. IOCTL handlers including `TDE_IOCTL_INDEXIO_READ` and `TDE_IOCTL_INDEXIO_WRITE` permit unprivileged user-mode callers to perform arbitrary hardware I/O port reads and writes without authorization checks. A local attacker can abuse this functionality to manipulate hardware registers, tamper with firmware-related interfaces, cause system instability, or establish persistent low-level compromise.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceThe Pegatron Tdelo64.sys kernel driver exposes a device interface (\\.\TdeIo) that allows arbitrary hardware I/O port reads and writes via IOCTL handlers TDE_IOCTL_INDEXIO_READ and TDE_IOCTL_INDEXIO_WRITE without any authorization checks, enabling unprivileged user-mode callers to gain kernel-level hardware access.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the Tdelo64.sys driver fileSearch for Tdelo64.sys in the Windows\System32\drivers directory and other driver search paths using 'dir /s C:\Windows\System32\drivers\Tdelo64.sys' or File Explorer searchAffected if The Tdelo64.sys driver file exists on the system
-
Check if the driver is loadedOpen an elevated command prompt and run 'sc query Tdelo' or check the driver list via 'driverquery /v | findstr -i tde' to see if the driver is loadedAffected if The Tdelo driver service exists and shows a running or stopped state
-
Verify the vulnerable device interface existsOpen a command prompt (non-elevated) and attempt to access the device via 'type \.\TdeIo' or use a tool like WinObj to check for the \GLOBAL??\TdeIo or \Device\TdeIo objectAffected if The device interface named 'TdeIo' is present in the object manager namespace
-
Test unprivileged IOCTL accessibilityUse a tool like ioctl.exe or write a small program to send TDE_IOCTL_INDEXIO_READ or TDE_IOCTL_INDEXIO_WRITE IOCTLs to \\.\TdeIo from a non-elevated user accountAffected if The IOCTL calls succeed without requiring administrative privileges, indicating the flaw is present
-
Check for the IOCTL handler presence in driverIf the driver file was found, examine it with a hex editor or disassembler for the strings 'TDE_IOCTL_INDEXIO_READ' and 'TDE_IOCTL_INDEXIO_WRITE' or the device name 'TdeIo'Affected if These IOCTL handler identifiers are present in the driver binary, confirming the vulnerable code path exists
The environment is affected if the Tdelo64.sys driver is installed and the TdeIo device interface is accessible to unprivileged users, allowing arbitrary I/O port operations without authorization.
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 dataApply vendor-supplied patch or update to Tdelo64.sys that implements proper authorization validation (e.g., check SeVerifyVolumeAccess or equivalent) in the affected IOCTL handlers before permitting hardware I/O operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14960 — 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-14960 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