Is CVE-2026-54000 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54000 being exploited in the wild.

How severe is CVE-2026-54000?

Informational severity, with a CVSS score of 7, published 10 July 2026.

Is there a fix for CVE-2026-54000?

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-54000 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-54000?

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.

CVE-2026-54000: osquery heap overflow in Windows processes table

CVE-2026-54000 · Severity: info · CVSS 7 · Published 2026-07-10

osquery is a tool used by security and IT teams to monitor and analyze the state of operating systems. A vulnerability in the Windows version allows a standard user to gain full administrative (SYSTEM) control of the computer. This occurs when osquery attempts to inspect a specially crafted malicious process, leading to a memory error that can be exploited to take over the system.

Technologies: Osquery. Vendors: Osquery.

Quick answers

Is CVE-2026-54000 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54000 being exploited in the wild.
How severe is CVE-2026-54000?: 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-54000?: 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-54000 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-54000?: 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 the Windows implementation of the osquery 'processes' table. The functions 'getProcessCommandLineLegacy()' and 'getProcessCurrentDirectory()' in 'processes.cpp' allocate a fixed 8192-byte buffer but use the 'Length' field from a target process's Process Environment Block (PEB) without validation when calling 'ReadProcessMemory()'. Since an attacker can manipulate the 'Length' field (a USHORT up to 65535 bytes) in their own process, they can trigger an out-of-bounds write of approximately 57KB. This can be leveraged for local privilege escalation (LPE) to SYSTEM when the osquery daemon (running with high privileges) queries the malicious process. The fix in version 5.23.1 introduces length clamping before the memory read operation.

Affected products

osquery osquery < 5.23.1

Timeline

2026-06-11: other: Fix PR submitted on GitHub
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

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.