How do I install the Cve Triage skill?

Run npx skillmds@latest add gabrielmoreira/cve-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cve Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cve Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cve Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cve Triage?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cve Triage by gabrielmoreira — Agent Skill

Name: Cve Triage
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

CVE Triage

Turn version/banner evidence from recon into a prioritized, exploitability-aware list of CVEs worth verifying. Use this after fingerprinting a service, when a banner or Server: header reveals a product and version, or whenever the target exposes software with a known version.

The `cve_lookup` tool

VulnClaw ships a read-only cve_lookup tool backed by NVD:

Keyword search — cve_lookup(query="Apache httpd 2.4.49", limit=5) returns the top CVEs sorted by CVSS, highest first.
CVE-ID detail — cve_lookup(query="CVE-2021-44228") returns the full record plus best-effort exploit / PoC repositories discovered on GitHub.

It performs no egress to the target and is safe during recon. Without an NVD_API_KEY it still works (lower rate limit); set one for heavier use.

Workflow

Extract product + version from recon — service banners, Server headers, JS bundles, login footers, package manifests. A precise version string (OpenSSH 8.2p1, nginx 1.18.0) yields far better matches than a bare name.
Query cve_lookup with "<product> <version>". Pull the detail record for any high/critical hit by re-querying its CVE-ID.
Score & prioritize — see references/cve-triage-workflow.md. Rank by CVSS, then by exploit availability, then by exposure (is the vulnerable surface actually reachable on this target?).
Confirm version applicability — match the target's version against the CVE's affected cpe range before claiming it. Banner ≠ proof of vulnerability.
Record findings with the CVE-ID, CVSS, and the evidence that maps this target to it. Mark unconfirmed version-only matches as needs-manual-review, not verified.

Pitfalls

A keyword match is a hypothesis, not a finding — version ranges and backported patches mean a banner version can be patched in place.
GitHub "PoC" repos are unverified third-party code; treat as leads, never run blindly against a target.
Prefer the CVSS base score for triage, but let exploit availability and real exposure override raw score when prioritizing verification effort.

---name: cve-triagedescription: CVE lookup and triage — map discovered services/versions to known CVEs via the cve_lookup tool, score by CVSS/exploitability, and prioritize what to verify first.--- # CVE Triage Turn version/banner evidence from recon into a prioritized, exploitability-aware list of CVEs worth verifying. Use this after fingerprinting a service, when a banner or `Server:` header reveals a product and version, or whenever the target exposes software with a known version. ## The `cve_lookup` tool VulnClaw ships a read-only `cve_lookup` tool backed by NVD: - **Keyword search** — `cve_lookup(query="Apache httpd 2.4.49", limit=5)` returns the top CVEs sorted by CVSS, highest first. - **CVE-ID detail** — `cve_lookup(query="CVE-2021-44228")` returns the full record plus best-effort exploit / PoC repositories discovered on GitHub. It performs no egress to the target and is safe during recon. Without an `NVD_API_KEY` it still works (lower rate limit); set one for heavier use. ## Workflow 1. **Extract product + version** from recon — service banners, `Server` headers, JS bundles, login footers, package manifests. A precise version string (`OpenSSH 8.2p1`, `nginx 1.18.0`) yields far better matches than a bare name. 2. **Query** `cve_lookup` with `"<product> <version>"`. Pull the detail record for any high/critical hit by re-querying its `CVE-ID`. 3. **Score & prioritize** — see `references/cve-triage-workflow.md`. Rank by CVSS, then by exploit availability, then by exposure (is the vulnerable surface actually reachable on this target?). 4. **Confirm version applicability** — match the target's version against the CVE's affected `cpe` range before claiming it. Banner ≠ proof of vulnerability. 5. **Record findings** with the CVE-ID, CVSS, and the evidence that maps this target to it. Mark unconfirmed version-only matches as needs-manual-review, not verified. ## Pitfalls - A keyword match is a *hypothesis*, not a finding — version ranges and backported patches mean a banner version can be patched in place. - GitHub "PoC" repos are unverified third-party code; treat as leads, never run blindly against a target. - Prefer the CVSS **base** score for triage, but let exploit availability and real exposure override raw score when prioritizing verification effort.

Frequently asked questions

Cve Triage