Skip to content

Exploit Database

The Resolve Platform's Exploit Database: exploit evidence by tier for everyone, and a Pro search over every exploit source, rule in the wild and sighting.

Updated 05 Nov 2026Markdown

Overview › Exploit Database (/resolve/exploit-database) answers “is there an exploit for this, and how serious is the evidence?” for a package and version or a vulnerability identifier. Use it before you rank a finding on exploitability, or to check a dependency you are about to adopt.

The page has two parts: the tier lens, which every visitor sees, and the catalogue, which is Pro.

Tier lens

One bar per evidence tier, on a shared scale. Each bar shows the number of records and the distinct CVEs inside them, in text beside the bar.

Tier Means
Mention Talked about, nothing runnable
Bounty Paid out by a bug bounty
Sighting Seen in attack traffic
Theoretical Proof of concept published
Weaponised Reliable exploit in toolkits
Known exploits On a known exploited list

Pressing a tier lists the CVEs that tier is busiest on. Pressing a CVE searches the catalogue for it on Pro. Below Pro it opens the CVE in Search Console instead, where the free existence signal shows whether exploits exist.

Catalogue

Three search fields filter as you type:

Field Example
Package google-chrome
Version 124.0.6367.60
Vulnerability ID CVE-2021-44228

Both searches resolve to a set of advisories, then to every record that references them. Results are one merged list of three record types:

Type Is
Exploits Exploit records from every source
Rules in the wild Snort and YARA detection rules linked to the CVE
Sightings Sighting counts from CrowdSec and VulnCheck XDB entries

Filters

  • Record type: all, exploits, rules in the wild or sightings.
  • Lane: Vulnesis Research Lab for Vulnesis’s own research, Canary for every other source.

The server applies both filters and returns counts over the whole result set, so the chip counts are not limited to the page on screen. Results come 50 to a page.

Record inspector

Opening a record shows it beside the list without leaving the page: its type and lane, linked CVEs, and where present the source, author, rule kind, published date, platform and sighting count. A series panel charts activity for the linked CVEs. Links lead to the Original record, the Source archive, and Open in Search Console.

The search terms, filters, page and open record are kept in the address bar, so a copied link opens a colleague on the same record.

Plan

The tier lens works for every visitor. The catalogue needs Pro or above, and the server enforces it. Below Pro the catalogue is drawn over sample data behind an upgrade prompt, and no search is sent.

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.