Quick answers
- Is CVE-2026-46388 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46388 being exploited in the wild.
- How severe is CVE-2026-46388?
- Medium severity, with a CVSS score of 4.4, published 10 July 2026.
- Which products and versions are affected?
- Osquery < 5.23.1.
- Is there a fix for CVE-2026-46388?
- 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-46388 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-46388?
- 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 vulnerability exists in osquery's file carving mechanism due to incorrect permission assignment (CWE-279) on temporary directories. When osquery 'carves' (collects) files, it creates a temporary directory to store the data before exfiltration; however, these directories were not created with private permissions, making them world-readable. A local, unprivileged attacker can monitor the temporary directory path and read the contents of the carved files before they are deleted upon completion. If an attacker can influence the target of a carve (e.g., a directory they control), they can leverage this to read arbitrary sensitive files like /etc/shadow. The issue is fixed in version 5.23.1 by ensuring carve directories are created with private permissions.
Affected products
- osquery osquery < 5.23.1
Timeline
- 2026-06-17: other: Pull request submitted to fix the issue
- 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