This week the 2026 Deloitte Technology Fast 500™ named us the 106th fastest-growing company in North America. Last week CRN added us to its Stellar Startup security vendors to know list, and back in August we came in at No. 478 on the Inc. 5000.
We're grateful and humbled by the recognition, but what's more exciting is why VulnCheck is being recognized.
Exploitation is now the number one cause of breaches
Verizon's DBIR has tracked how breaches start for years. This is the first time vulnerability exploitation has come out on top at 31%, a year ago it was 20%. Google's M-Trends report has had exploitation in first place six years in a row, most recently at 32%.
AI is finding vulnerabilities faster than anyone can fix them. This month the industry passed 100,000 CVEs for 2026, which is more than double from last year.
The reality is most vulnerability tooling, processes, and data sources weren't designed for this volume or speed. There is an assumption there's time for disclosure details to trickle in, for an analyst to read each advisory, and for patching to take weeks. Teams don't have the luxury of time anymore. They're being asked to react in hours or days.
Get the intelligence without maintaining the sources
Of the 100,000+ CVEs published this year, VulnCheck KEV has tracked 1,363 as exploited in the wild by November 1, or about 1.4% of vulnerabilities. Those are the ones our customers say they are addressing first. The hard part? Knowing which vulnerabilities are exploited, and knowing early.
So most teams go and get the data themselves. Someone writes a script to pull from NVD, then another for CISA KEV, then vendor advisories, exploit repositories, and threat reports, and before long there's a pile of collectors that somebody has to keep running. That's engineering time and budget that isn't going toward the work the team was hired to do.
The old way was to wait for public databases to catch up and then have an analyst work through the list. The new way is verified intelligence that shows up early and goes straight into your systems. That's what VulnCheck delivers, in a machine-native form built for your data lakes, ETL pipelines, automation, and AI and LLM workflows.
A few things change when a team makes that switch.
- 500+ sources, and you don't maintain any of them. Our research team collects and enriches them, which means your engineers can stop writing collectors.
- Data you can rely on. NVD has had an enrichment backlog since February 2024. The Commerce Department's Inspector General looked into it this spring and said it's undermining the database's utility and public trust. CISA KEV has a different limit, which is that it's scoped for federal remediation. We identified 884 known exploited vulnerabilities in 2025. CISA added 245.
- Earlier warning. On vulnerabilities that both catalogs list, VulnCheck KEV had them 28 days before CISA KEV on average. Our canaries were a median of 14 days ahead of the next public source. Two to four weeks is a lot of time to plan a response.
- Depth you can't get from aggregation. We add our own first-party data to what's public. CPE is one example, and we kept generating it after NIST narrowed NVD enrichment. Canary Intelligence is the other. Our canaries are real vulnerable systems, not emulators, so they record who exploited a vulnerability, what payload they ran, and where it called back to. That came to 1.98 million exploitation events in 13 months, and for 65+ vulnerabilities there is still no other public evidence.
Every security team asks the same question
Is this exploitable, is it being exploited, and what do we do about it? A vulnerability management team asks that when it's deciding what to patch, but it's far from the only team asking.
- Threat intelligence wants to know which CVEs threat actors, ransomware groups, and botnets are exploiting right now.
- Vulnerability and exposure management rank findings by exploitation evidence, and lean on it to justify emergency patching.
- Attack surface management looks for internet-facing assets exposed to initial-access vulnerabilities.
- Pentesters and red teams pull vetted exploits so they can test the paths threat actors are taking.
- The SOC, detection engineers, and threat hunters write and validate detection rules, then hunt with attacker IPs and C2 infrastructure.
- Network security blocks known attacker infrastructure at the firewall.
- Incident response needs the initial access vector, and a fast answer to "are we affected?" when a new exploited CVE lands.
- AppSec and product security sort open-source dependency findings by what's being exploited.
- Security engineering wires it into existing tools, playbooks, and AI agents through the API.
Security vendors build it into their own products so their customers get faster, more complete answers. Government agencies rely on vulnerability exploit intelligence to protect critical infrastructure and defend national networks at the perimeter.
That's the shift we think this year's recognition is pointing at. Exploit intelligence used to be one team's tool. Now whole security organizations, the vendors that serve them, and governments are building on it.
What comes next
CVE volume isn’t going back down, and exploitation will continue to follow. Our job is to get the evidence to you as early as it exists. To our customers, our partners, and everyone on this team, thank you.
VulnCheck Community is free and includes VulnCheck KEV, NVD++, the VulnCheck Exploit Database (XDB) and Initial Access Community, join today and see for yourself.