osquery is a SQL powered operating system instrumentation, monitoring, and analytics framework. Prior to 5.23.1, on Windows, a local unprivileged attacker can cause a heap buffer out-of-bounds write if there is a query of the processes table targeting a maliciously crafted process, due to unchecked PEB string lengths in process command-line and current-directory reads. If exploited successfully, this could allow a potential local privilege escalation from standard user to SYSTEM. This issue is fixed in version 5.23.1.
CVE-2026-54000
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(medium)
- EPSS
- 1.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 14, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Heap buffer overflow via `processes` table (Windows) · Advisory · osquery/osquery · GitHub
https://github.com/osquery/osquery/security/advisories/GHSA-4r78-6hg6-33gg5.23.1
Patch available: osquery/osquery 5.23.1
https://github.com/osquery/osquery/releases/tag/5.23.1Fix heap buffer overflow in Windows processes table (GHSA-4r78-6hg6-33gg)
Fix merged in osquery/osquery PR #8934 on 2026-06-17 — awaiting tagged release
https://github.com/osquery/osquery/pull/8934commit 3d457c412eb0 (osquery/osquery)
Fix landed in osquery/osquery commit 3d457c412eb0 — awaiting tagged release
https://github.com/osquery/osquery/commit/3d457c412eb0c986b0c37d8903edae8bc9f9e246Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 23:18 UTCEG score recompute
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 11:55 UTCEG score recompute
- 2026-07-13 00:32 UTCEG score recompute
- 2026-07-12 13:09 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:46 UTCEG score recompute
- 2026-07-11 14:23 UTCEG score recompute
- 2026-07-11 03:00 UTCEG score recompute
- 2026-07-10 15:38 UTCEG score recompute
- 2026-07-10 15:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
Frequently asked(5)
What is CVE-2026-54000?
When was CVE-2026-54000 disclosed?
Is CVE-2026-54000 actively exploited?
What is the CVSS score of CVE-2026-54000?
How do I remediate CVE-2026-54000?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54000
Is Your Infrastructure Affected by CVE-2026-54000?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.