Skip to main content

osquery CVE-2026-54001

| EUVDEUVD-2026-42918 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-07-10 GitHub_M
7.0
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Standard user logs into Windows host
  2. Delivery
    Plant maliciously crafted binary on disk
  3. Exploit
    osquery authenticode query targets file
  4. Execution
    Malformed publisher parsed in getOriginalProgramName
  5. Persist
    Heap out-of-bounds write corrupts memory
  6. Impact
    Code execution as SYSTEM

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a local, already-authenticated standard user on a Windows host running osquery (PR:L), the ability to write a maliciously crafted binary to a location osquery can read, and a query of the authenticode table that targets that binary - the malicious publisher information is parsed by getOriginalProgramName during that query (UI:P, the query acts on the attacker's file). Limiting factors: it is Windows-only, needs local access rather than network reach, affects only osquery versions before 5.23.1, and depends on osquery actually running an authenticode query against the attacker-controlled file (e.g., a scheduled query or an operator running one); privilege escalation to SYSTEM only materializes when the osquery process is running with SYSTEM privileges.

Impact

The supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H, base 7.0) is internally consistent with the description: local access, low complexity, low privileges already required, and passive user interaction (a query must reach the malicious binary), yielding high confidentiality/integrity/availability impact but no subsequent-system scope change. Real-world risk is bounded by the local attack vector and the dependency on osquery actually querying the authenticode table against the attacker's file - this is not a remotely reachable or network-wormable issue, so EPSS would be expected to be low. No KEV listing and no POC were provided, so this is a credible but not urgent-in-the-wild issue; priority rises sharply in environments that deploy osquery fleet-wide as a SYSTEM service and run scheduled authenticode queries. Missing signals: EPSS score and SSVC decision data were not supplied and cannot be inferred.

Exploit ScenarioDerived

A standard user drops a specially crafted signed (or malformed-signature) binary onto the host, then waits for-or induces-an osquery query against the authenticode table that targets that file, such as a fleet-wide scheduled query enumerating executables. Parsing the malicious publisher fields in getOriginalProgramName triggers the heap out-of-bounds write inside the SYSTEM-level osquery process, potentially yielding SYSTEM-level code execution. No public POC was provided, so exploitation is theoretical at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 10, 2026

Local privilege escalation in osquery on Windows prior to 5.23.1 lets a standard user escalate to SYSTEM by planting a maliciously crafted binary and having the authenticode table query it, triggering a heap out-of-bounds write in the getOriginalProgramName publisher-parsing routine. The flaw is a CWE-122 heap buffer overflow reachable whenever osquery (typically running as SYSTEM) evaluates authenticode publisher metadata against attacker-controlled files. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; EPSS was not provided.

RemediationAI

Upgrade to the vendor-released patch: osquery 5.23.1 (https://github.com/osquery/osquery/releases/tag/5.23.1), which contains the fix (PR https://github.com/osquery/osquery/pull/8923, commit 59a808cda96d5a089cf6ec147efe152459284d54); see advisory GHSA-hr28-jvpx-68cx (https://github.com/osquery/osquery/security/advisories/GHSA-hr28-jvpx-68cx). Until patched, reduce exposure by avoiding or restricting scheduled and ad-hoc queries against the authenticode table on Windows endpoints, and by limiting where standard users can write executable files that osquery would enumerate (for example, tightening ACLs on user-writable directories); the trade-off is reduced code-signing visibility from osquery while the mitigation is in place. Because exploitation requires a local low-privileged foothold, standard endpoint hardening and least-privilege on where unprivileged users can drop binaries further limits reachability.

Affected VersionsENISA

osquery < 5.23.1

Affected Packages

euvd osquery fix: 5.23.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

osquery is an open-source, SQL-driven operating-system instrumentation and monitoring framework (CPE cpe:2.3:a:osquery:osquery). On Windows it exposes an authenticode virtual table that inspects Portable Executable (PE) code-signing data. The defect lives in getOriginalProgramName, which parses Authenticode publisher/subject information embedded in a signed binary; malformed publisher fields cause a heap-based out-of-bounds write (CWE-122). Because the osquery agent frequently runs as a SYSTEM service and queries file metadata across the filesystem, corrupting its heap while it parses an attacker-supplied binary provides a path to code execution in that privileged context.

Know when Osquery gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.0 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.3 HIGH

Local low-privileged user (PR:L, AV:L) needs a query to touch the malicious binary (UI:R); heap overflow in the SYSTEM process yields full C/I/A impact with no cross-system scope change.

3.1 AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Jul 10, 2026 - 17:01 EUVD
CVE Published
Jul 10, 2026 - 14:49 cve.org
HIGH 7.0

DescriptionCVE.org

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 authenticode table targeting a maliciously crafted binary, due to publisher information parsing in getOriginalProgramName. 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.

Executive ViewAI

Why It Matters

osquery on Windows versions prior to 5.23.1 contain a privilege escalation vulnerability allowing standard users to become system administrators. This enables unauthorized system control and disables endpoint monitoring on affected assets, compromising security infrastructure for organizations using this monitoring tool.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict standard user file system write permissions to prevent malicious binary placement, deploy endpoint detection and response (EDR) monitoring to detect privilege escalation attempts, isolate osquery agents in segmented network environments, disable authenticode table functionality if operational requirements permit.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Medium
widely used open-source endpoint monitoring agent, common in security-conscious enterprises
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy