{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54000 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54000 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54000 is a high-severity memory corruption vulnerability in osquery, published on 10 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54000 and fix it if it is affected.\n\nWhat it is: CVE-2026-54000 is a high-severity memory corruption vulnerability in osquery, published on 10 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-54000 in the wild and no public exploit code.\n\nAffected product: osquery. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54000/ (Markdown: https://insights.sbomify.com/CVE-2026-54000/index.md)","id":"CVE-2026-54000","markdown":"https://insights.sbomify.com/CVE-2026-54000/index.md","name":"CVE-2026-54000","record":{"aliases":["GHSA-4r78-6hg6-33gg"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"osquery monitoring agent","requires_auth":"low_privilege","summary":"A local attacker can trigger a heap buffer overflow in osquery on Windows to escalate privileges from standard user to SYSTEM.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"osquery: Heap buffer overflow in `getProcessCurrentDirectory()` via `processes` table (Windows)","id":"CVE-2026-54000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"osquery: Heap buffer overflow via `authenticode` table (Windows)","id":"CVE-2026-54001"},"packages":[],"prev":{"headline":"Radius Controller May Delete a Container Resource via an Injected Deployment Annotation (Multi-Tenant Installs)","id":"CVE-2026-53999"},"products":["osquery"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["osquery"]},"summary":"A local attacker can trigger a heap buffer overflow in osquery on Windows to escalate privileges from standard user to SYSTEM.","url":"https://insights.sbomify.com/CVE-2026-54000/"}