cve-intelligence-lookup

Queries authoritative CVE sources and vets public exploit code with provenance and reliability scoring.

1|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Yenn503/Net-Runners --skill cve-intelligence-lookup-yenn503
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cve-intelligence-lookup
Source: https://github.com/Yenn503/Net-Runners/tree/main/.netrunner/skills/infra/cve-intelligence-lookup
Command: npx skills add https://github.com/Yenn503/Net-Runners --skill cve-intelligence-lookup-yenn503

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers who fingerprint a product and version need trustworthy exploit intelligence, but public PoCs are unvetted and often unsafe. This Skill enforces a disciplined lookup workflow across authoritative sources so exploit leads are validated before use. ## Core Features & Use Cases - Tiered source hierarchy: Queries the local arsenal cache, Exploit-DB via searchsploit, CISA KEV, NVD, nuclei-templates, and PoC-in-GitHub in a defined trust order. - Trust and provenance discipline: Requires reading PoC source, recording source URLs and references, scoring reliability (high/medium/low/unverified), and detonating untrusted code in an isolated VM. - Arsenal integration: Feeds validated leads into .netrunner/arsenal/index/*.yaml entries and appends confirmed exploits to discovered.jsonl for reuse. - Use Case: After fingerprinting a target running a specific product version, query the arsenal and CISA KEV to find an actively exploited CVE, confirm it with a nuclei template, then record a provenance-tagged arsenal entry. ## Quick Start Ask the agent to look up known CVEs and vetted exploits for the fingerprinted product and version, prioritizing CISA KEV and Exploit-DB results.

Frequently Asked Questions about cve-intelligence-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a CVE is actively exploited in the wild?▼

Query the CISA Known Exploited Vulnerabilities catalog by fetching its JSON feed from cisa.gov. A CVE listed in KEV is confirmed as actively exploited and should be prioritized over other leads.

How do I find exploit code for a specific product version?▼

Use searchsploit with the product and version to query the offline Exploit-DB mirror, then use searchsploit -m to copy the exploit locally. Prefer this vetted archive over random GitHub repositories.

Is it safe to run public PoC exploits from GitHub?▼

No. Public PoCs are treated as unverified until every line is read and understood, including network callbacks. Untrusted PoCs should be detonated in an isolated VM, never on the operator host.

How do I confirm a CVE is present before exploitation?▼

Use nuclei with the CVE detection templates, for example nuclei -t http/cves/ -tags <cve>, after updating templates. Also match the target's exact version against the CVE's affected range from NVD.

What data sources does CVE lookup query first?▼

The local arsenal cache is queried first via ArsenalLookup or nr_arsenal_lookup, since it contains curated, provenance-tagged entries. External sources like Exploit-DB, CISA KEV, and NVD follow in a defined trust order.