exploits-search

To search for exploits across vulnerabilities, apply filters for ecosystem, severity, exploit source, and EPSS score. This surfaces exploitable CVEs specifically relevant to your project's tech stack and dependencies.

EPSS filtering ranks exploit opportunities by predicting the likelihood of vulnerability exploitation in the wild. This allows teams to prioritize proactive risk assessment based on actual threat probability rather than just severity.

Yes, you can filter exploitable CVEs by ecosystem and severity. This tailors vulnerability findings to your specific project needs, ensuring the discovered exploits directly map to your repository's tech stack.

Vulnerability discovery cross-references scans by reading prior memory state from .vulnetix/memory.yaml. It updates memory by creating stub entries with status under_investigation and appending findings to the history.

The best way to plan remediation after finding exploited vulnerabilities is to use the results for deep analysis. You can proceed to targeted remediation planning to address the surfaced exploit opportunities.

Automated exploit discovery relies on existing memory state and cross-referenced scans, meaning it may create stub entries marked under_investigation rather than providing immediate, fully verified exploit confirmations.