CVE-2026-54001

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Heap buffer overflow via `authenticode` table (Windows) · Advisory · osquery/osquery · GitHub

https://github.com/osquery/osquery/security/advisories/GHSA-hr28-jvpx-68cx
github_release Patch Available

5.23.1

Patch available: osquery/osquery 5.23.1

https://github.com/osquery/osquery/releases/tag/5.23.1
github_pr

Switch authenticode getOriginalProgramName to CryptDecodeObjectEx

Fix merged in osquery/osquery PR #8923 on 2026-06-23 — awaiting tagged release

https://github.com/osquery/osquery/pull/8923
github_commit

commit 59a808cda96d (osquery/osquery)

Fix landed in osquery/osquery commit 59a808cda96d — awaiting tagged release

https://github.com/osquery/osquery/commit/59a808cda96d5a089cf6ec147efe152459284d54

Weakness 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.

  1. 2026-07-14 00:01 UTCEG score recompute
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 12:32 UTCEG score recompute
  4. 2026-07-13 01:03 UTCEG score recompute
  5. 2026-07-12 13:34 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 02:07 UTCEG score recompute
  8. 2026-07-11 14:36 UTCEG score recompute
  9. 2026-07-11 03:08 UTCEG score recompute
  10. 2026-07-10 15:38 UTCEG score recompute
  11. 2026-07-10 15:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54001?
CVE-2026-54001 is a high vulnerability published on July 10, 2026. 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…
When was CVE-2026-54001 disclosed?
CVE-2026-54001 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54001 actively exploited?
CVE-2026-54001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54001?
CVE-2026-54001 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54001, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54001

Explore →

Is Your Infrastructure Affected by CVE-2026-54001?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.