Live › vulnerability › CVE-2026-116776
Go to dashboardUSB Test, a Windows command-line tool for checking USB flash drives, trusts the sector size a drive reports without validating it. A malicious USB storage device can report a tiny or zero sector size, causing heap out-of-bounds writes that crash the elevated app or may allow arbitrary code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 16:33 UTC. All times on this page are UTC.
Teams that run USB Test on Windows to verify flash drives are exposed when they start a drive test on a device they did not trust. The exposure comes from the physically attached USB storage device reporting a bad sector size, so only machines that run the test against untrusted drives matter. Teams that never run this tool, or only test drives they control, can skip it.
No product ranges from the sources yet.
1.1.51.1.5 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
USB Test is a lightweight Windows CLI utility for verifying sector integrity and detecting overreported capacity on USB flash drives. Prior to version 1.1.5, getSectorSize() in USB Test/src/driveinfo.cpp trusts DISK_GEOMETRY.BytesPerSector returned by IOCTL_DISK_GET_DRIVE_GEOMETRY without checking whether the call succeeded or enforcing size bounds. USB Test/src/drivetest.cpp uses the value for division and to size a heap buffer before memcpy(buffer.data(), §or, 8), so a physically connected malicious USB storage device can report a value below eight bytes and cause repeated out-of-bounds writes, or report zero and cause a divide-by-zero denial of service when a user starts a drive test. The heap corruption can crash the elevated application and may permit arbitrary code execution. This issue is fixed in version 1.1.5.
This page as .md · .json · in your agent: get_signal("CVE-2026-116776")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.