Vulnerability
CVE or product issue
Browse CVEs, then validate affected scope before assigning work or reporting risk.
Explore
Find the signal, then connect it to the next step.
Explore is for CVEs, advisories, KEV, vendors, products, campaigns, and source context. It should lead to validation, action, reporting, or practice.
Start Points
What kind of security information do you have?
Each route includes a recommended follow-up so exploration turns into useful movement.
Advisory
Vendor or agency guidance
Review advisories and source differences before treating fixed-version or affected-range language as local proof.
Known exploited
KEV or active pressure
Use exploitation signals as urgency context, then check exposure, affected status, and owner action.
Vendor or product
Track affected ecosystems
Review vendor and product pressure, analytics, and source history before prioritizing a product family.
Threat context
Campaigns, actors, and detection
Use campaign and detection pages to orient defensive work without treating public context as proof of local compromise.
Recommended after exploring: validate applicability, choose an action lane, write the handoff or brief, then practice the same decision with fictional data.