Approach
We try to review whole codebases if possible, including their transitive dependencies. The method works
in two stages. First, an AI-assisted pipeline sweeps every repository at a scale no single auditor could
cover by hand, and where possible builds a working PoC for each candidate. Second, a human
researcher triages every candidate, discards the false positives, and traces each real bug to its root
cause. Many candidates are discarded as not exploitable. The validation,
the written report, and any fixes are led by humans, with AI helping along the way.
The outcome is a security report covering the components we review, a set of responsibly disclosed
findings, and, where feasible, fixes contributed back to the project.
Track record
30+ CVEs and confirmed findings in software used by millions
58 merged open-source pull requests
The findings span browsers, infrastructure and developer tools, and range from
memory-safety issues deep in C and C++ to web and injection bugs in JavaScript.
-
CVE-2026-8558
Google Chrome
Out-of-bounds write in the font path allowing remote code execution inside the
sandbox. Rated High, CVSS 8.8. Chrome VRP reward.
-
CVE-2026-4699
Mozilla Firefox
Incorrect boundary conditions in Layout, Text and Fonts. Rated High, published
as MFSA 2026-20.
-
CVE-2026-41148
Mermaid
CSS injection from improper sanitization in the JavaScript diagramming library.
Code injection, CWE-94. Fixed upstream.
Other confirmed findings include Keycloak, Apache ActiveMQ, Spotify, Rancher, Argo, Home
Assistant, Sentry, NetworkManager, Gitea, Vim and others.