dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-14961

MEDIUM · 6.2 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click 5 weeks old

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 · unedited
Pegatron `Tdelo64.sys` exposes a privileged device interface, `\\.\TdeIo`, that fails to properly restrict access to sensitive IOCTL functionality. The driver's IOCTL dispatcher does not validate caller privileges or verify user-supplied kernel memory addresses before performing memory operations. By sending crafted requests to IOCTL, a local attacker can achieve arbitrary kernel memory read and write operations, leading to privilege escalation to `NT AUTHORITY\SYSTEM`, security product bypass, credential theft, or complete system compromise.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 4d ago

Surfaced 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 confidence

The Pegatron Tdelo64.sys driver exposes a privileged device interface (\\.\\TdeIo) that lacks proper access controls. Its IOCTL dispatcher fails to validate caller privileges and does not verify user-supplied kernel memory addresses before performing memory operations, allowing a local attacker to achieve arbitrary kernel memory read/write and escalate to NT AUTHORITY\SYSTEM.

MitigationDisable or remove the vulnerable Tdelo64.sys driver if not required for system operation. If required, apply vendor-supplied patches that add proper privilege validation and kernel memory address verification in the IOCTL dispatcher.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Tdelo64.sys driver exists on the system
    Search for Tdelo64.sys file in system directories: check C:\Windows\System32\drivers\ and use 'dir /s C:\*Tdelo64.sys' or Get-ChildItem -Path C:\ -Recurse -Filter Tdelo64.sys -ErrorAction SilentlyContinue
    Affected if The Tdelo64.sys file is found in any system directory
  2. Check if the Tdelo64.sys driver is loaded
    Run 'sc query Tdelo64' or 'driverquery /v | findstr Tdelo64' to query the driver service status, or use 'fltenum.exe' or similar driver enumeration tools
    Affected if The driver appears in the list of loaded/running drivers with a running state
  3. Verify if the vulnerable device interface exists
    Use Sysinternals WinObj or run 'devicequery' to enumerate device objects and check for \Device\TdeIo or \GLOBAL??\TdeIo, or inspect output from 'sd \.\TdeIo' if available
    Affected if The \.\TdeIo device interface is present and accessible on the system
  4. Check driver version information
    Right-click Tdelo64.sys file, select Properties > Details, or use 'powershell (Get-Item "C:\Windows\System32\drivers\Tdelo64.sys").VersionInfo' to retrieve file version metadata
    Affected if A version exists but cannot be compared to fixed releases (no patched version range documented); any version found is potentially vulnerable
  5. Confirm the IOCTL dispatcher is reachable
    Attempt to open the device with CreateFile("\\.\\TdeIo", ...) and send IOCTLs using a tool like ioctlbf or write a test application that communicates with the device - verify no privilege check is performed
    Affected if The device can be opened and IOCTL calls succeed without requiring elevated privileges or returning access denied errors

If the Tdelo64.sys driver is loaded and the \.\TdeIo device interface exists on the system, the environment is affected by this vulnerability because the IOCTL dispatcher lacks proper privilege validation and kernel memory address verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or remove the vulnerable Tdelo64.sys driver if not required for system operation. If required, apply vendor-supplied patches that add proper privilege validation and kernel memory address verification in the IOCTL dispatcher.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14961 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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