Resources › CVE intelligence

AI is finding vulnerabilities faster than anyone can act on them

We curate the intelligence that tells you which ones reach you: what each CVE needs, which builds are really fixed, and what attackers are doing now, kept current. Read about some of the recent and high-profile ones here, or give your agent all of it through our MCP server.

The research you wish you had while responding

Whether it arrives as a CVE, a vendor bulletin or a quiet fix in a commit, the first day goes to research: the advisory if there is one, every distribution's tracker, vendor blogs that disagree with each other, all to answer whether it reaches you and whether you're really patched. A week later you're back at it, because a patch turned out to be incomplete or exploitation started. We do that research for you and keep it current, so your team can spend those hours on containment and remediation. Explore our work on some of the recent and high-profile CVEs.

VulnerabilityWhat decides exposureUpdated
nginx2rootCVE-2026-123007 · CVE-2026-123633 · NGINX Any nginx with HTTP/2 on for a reachable listener; one of the two bugs also needs the request to open an outbound connection. Version strings mislead both ways. 20 Nov 2026
Java4ShellCVE-2026-114938 · OpenJDK, GraalVM Only x86-64 CPUs with AVX-512 VBMI, and only when the running JVM leaves the fast Base64 decoder on. Version strings mislead both ways. 19 Nov 2026
PHP2ShellCVE-2026-109618 · CVE-2026-109619 · PHP Any PHP that takes network input. The first patch was incomplete on 8.3 to 8.5: fully fixed at 8.2.35, 8.3.37, 8.4.28 or 8.5.13. 19 Nov 2026

Why a version match isn't enough anymore →   How this intelligence grounds your agent →