package.json, requirements.txt, Cargo.toml, etc.) and cross-references dependencies against the OSV (Open Source Vulnerabilities) database to profile open-source supply chain risk.
field:value rules — multiple rules are ANDed together automatically:
| Rule | What it does |
|---|---|
vendor:cisco | CVEs affecting Cisco. Use a comma list for "any of" — vendor:cisco,juniper |
product:"windows server" | Quote multi-word product names |
cvss>=9 | CVSS base score threshold. Operators: >= <= > < = |
epss>=0.7 | EPSS exploit-probability threshold (0–1). epss_pct>=90 filters by percentile (0–100) |
kev:true | Actively exploited (CISA KEV) only |
actionable:true | In CISA KEV or EPSS ≥ 0.1 — the small slice actually worth prioritizing |
ransomware:true | KEV entries with known ransomware-campaign use |
exploit:true | Has a known public PoC/exploit |
cna:github | Which authority assigned the CVE (cna:github,vulncheck for "any of") |
ai:true | Credited to an autonomous AI agent. discovery:bug_bounty for other channels (fuzzers, bounties, vendor teams) |
enrichment:high | Record completeness — complete / high / medium / low / stub |
-backfilled:true | Drop records published years after their ID was reserved |
year:2026 | Published in a given year. cve_year:2019 filters the year in the CVE ID instead |
after:2026-01-01 | Published on/after this date (before: also works) |
status:rejected | Withdrawn/duplicate CVE records (hidden by default; status:all shows both) |
-vendor:oracle | A leading - excludes a match instead of requiring it |
vendor:cisco,juniper kev:true cvss>=9 -product:ios. Whatever you type also becomes your feed: click "RSS feed for this view" on the CVE Monitor page to subscribe to that exact filter, or add &format=rss to the page URL yourself.
?search=) still works for any links you already have — it's being phased out in favor of the rule syntax above, not removed outright.