osquery

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability Separately, for a merged upstream patch : up to $5,000 Google Patch Rewards pays for a patch you get accepted upstream and that stays merged, without reverts, for one month. It does not pay for the report. This is a Tier 2 project, in scope through its OSS-Fuzz integration, so $5,000 is the reachable ceiling; the $15,000 headline and the 2× and 3× memory-safety multipliers are Tier 1 only. Awards start at $100, the patch has to be between one and twelve months old, submissions are capped at three per person per month, and one-liner fixes for non-exploitable crashes are not rewarded. Sanctions and territory exclusions apply. CVE history 3 Last 12 months 9 Lifetime Memory safety 40 % Access control 25 % Info disclosure 20 % Injection 10 % Latest advisories Loading the feed Overview osquery is the endpoint telemetry substrate of modern security operations. It runs as a root or SYSTEM daemon on Linux, macOS and Windows fleets measured in millions of endpoints, and it is the data layer under Fleet, Kolide, Uptycs and a great deal of in-house detection engineering. The process is high-privilege by design: it reads the process table, kernel event streams, keychains and file contents, and it takes configuration and distributed queries from a remote TLS server. Two HIGH-severity heap overflows in the Windows processes and authenticode tables shipped in July 2026 with no money attached by anybody. The project pays nothing for a report, so sorona.xyz pays you directly on qualified, reproduced findings. In scope SECURITY.md asks for a private GitHub advisory on osquery/osquery , and that repository is the boundary: the old facebook/osquery path only redirects to it The whole virtual-table layer on every platform, meaning every table that shells out to or parses operating-system structures on Linux, macOS and Windows The SQLite integration and query planner in full, including the ATTACH surface and everything a query can reach through it The remote TLS pathway end to end: enrolment, the config plugin, the logger plugin and distributed queries, where a hostile or spoofed server drives an agent running as root File carving and the extensions socket, plus the osqueryd watchdog, all of which are reachable from a lower-privileged local user The platform event subsystems the daemon subscribes to, covering auditd and BPF on Linux and the endpoint security and keychain paths on macOS, all executing with full privilege Configuration and flag handling, including anything that changes what the daemon reads or where it sends results Out of scope Fleet, FleetDM, Kolide and the other commercial osquery management servers, which are separate products built on top of this agent Third-party osquery extensions that do not live in this tree The Meta bug bounty as a pathway: osquery left the facebook org in 2019 and that coverage did not follow it One-liner non-exploitable crash fixes, which the reward rules place below the bar Patches younger than one month or older than twelve, which the reward age window excludes at both ends Anything not merged upstream, and anything reverted within the first month after it lands Most-valued findings Memory corruption in a virtual table driven by content the agent enumerates rather than trusts. The Windows processes and authenticode overflows are the reference shape, memory safety is the largest class here, and the process is running as SYSTEM when it happens A hostile or spoofed TLS server reaching code execution or arbitrary configuration through the remote enrolment, config or distributed-query plugins, which turns one compromised management channel into an entire fleet Local privilege escalation from an unprivileged user through the extensions socket, the watchdog or file carving, since those are the surfaces a low-privileged attacker can already touch Information disclosure that lets an unprivileged user read carved file contents, keychain material or other telemetry the daemon collects with root access SQL injection or query-planner abuse through the SQLite integration, the class CVE-2020-26273 landed in, where an attacker-influenced query reaches more of the host than the caller intended Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report privately through GitHub's security advisory form on osquery/osquery , as the project's SECURITY.md directs, rather than opening a public issue Send something reproducible against a current build; the project assigns CVEs and ships coordinated advisory batches, and a triager needs to see the bug The finding has to live in osquery/osquery itself: the old facebook/osquery path only redirects, and no Meta bounty coverage came with the move If you also want the Google patch money, land the fix upstream yourself and keep it merged without reverts for one month, with the patch between one and twelve months old; that is a separate pathway with its own rules One-liner fixes for non-exploitable crashes are not rewarded on the Google side, and submissions there are capped at three per person per month Google cannot pay anyone on a sanctions list or resident in Russia or Belarus Disclosure Coordinated through a private GitHub Security Advisory on osquery/osquery . The project uses that process properly, assigns CVEs and publishes advisories in coordinated batches, so hold the detail until the advisory is public; there is no confidentiality or embargo term on the Google side to work around. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability