PROBER
$ login
// mission Threat Intelligence · Real Time

Vulnerability
assessment for
technical teams.

Describe your tech stack. Prober maps it against the public vulnerability graph and returns a prioritized list of fixes, written for the technologies you use.

$ continue with google./how-it-works
prober — scan.session
$ prober scan --stack=acme-prod
[01:23:14] resolving stack manifest...
[01:23:14] components= 42 pinned
[01:23:15] source= cve-list-v5
[01:23:16] applying ssvc decision tree...
[01:23:17] ▸ ACT openssl@3.0.7 CVE-2024-2511
[01:23:17] ▸ ATTEND postgres@15.4 CVE-2024-10978
[01:23:18] ▸ TRACK curl@8.4.0 CVE-2024-2398
[01:23:19] writing findings to workbench...
✓ 28 findings · 4 act · 9 attend · 15 track
$
ACT
fix now
exploited or trivially exploitable
ATTEND
schedule
elevated risk · plan a window
TRACK
observe
low signal · keep watch
// how it works

Three modules. One pipeline.

Manifest in, prioritized work list out. Each step is inspectable; nothing is hidden behind a black box.

module 01
Compose your stack
Pick a persona — web app, data pipeline, internal tool — and the catalog seeds a representative manifest. Pin the exact versions you run.
▸
Persona-driven starter stacks
▸
Category-grouped tech catalog
▸
Version pinning per component
module 02
Scan & triage
Each scan correlates pinned versions against CVE-list-v5, scores them with CVSS, and routes every finding through the SSVC decision tree.
▸
CVE-list-v5 advisory matching
▸
CVSS severity scoring
▸
SSVC tiers · act · attend · track
module 03
Workbench
Drill into any finding to see the affected and fixed versions on a timeline, the SSVC reasoning, and the upstream commits that resolve it.
▸
Affected → fixed version timeline
▸
SSVC verdict & context keys
▸
Upstream fix commits per CVE
// begin
Triage your stack in under five minutes.
$ continue with googlehow it works