Quick answers
- Is CVE-2026-54001 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54001 being exploited in the wild.
- How severe is CVE-2026-54001?
- Informational severity, with a CVSS score of 7, published 10 July 2026.
- Which products and versions are affected?
- Osquery < 5.23.1.
- Is there a fix for CVE-2026-54001?
- A patch was published on 2026-06-24: Version 5.23.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54001 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-54001?
- Check whether you run Osquery at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer overflow (CWE-122) exists in osquery's Windows implementation of the authenticode table. The vulnerability is located in the getOriginalProgramName function, where a call to CryptDecodeObject incorrectly used a pointer to the signer_information buffer as the output destination instead of the dedicated, correctly-sized publisher_info_blob_ptr buffer. An attacker can exploit this by placing a crafted Portable Executable (PE) file with a large SPC_SP_OPUS_INFO attribute on the system; when osquery queries this file's signature data, it triggers an out-of-bounds write. This can lead to local privilege escalation from a standard user to SYSTEM. The issue was resolved in version 5.23.1 by migrating to the CryptDecodeObjectEx API with the CRYPT_DECODE_ALLOC_FLAG to ensure safe buffer management.
Affected products
- osquery osquery < 5.23.1
Timeline
- 2026-05-20: other: Initial fix developed
- 2026-06-24: patched: Version 5.23.1 released
- 2026-07-01: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: CVE published to NVD