Individual skill
redteam-cve-validation
CVE validation domain card. Use after CVE lookup has produced applicable or candidate CVEs and red-team mode needs scoped evidence to decide whether to continue, pivot, or report.
deepsec/spear/skills/specialized/redteam-cve-validation/SKILL.md
Source commit fff031fc01fb36b95348214c8ee359f6ede8aa8b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 509
- Repository last updated
- Aug 24, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agents Repository topic
- aisecurity Repository topic
- cybersecurity Repository topic
- plugin Repository topic
- security Repository topic
- vscode Repository topic
- vulnerability Repository topic
- hacker Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,478 bytesreferences/upstream-source.mddoc · 213 bytes
Read excerpt
# CVE Validation
## Domain
Validate candidate CVEs against the current target evidence without assuming exploitability.
The module consumes `cve_candidate_list`, product/version evidence, service fingerprints, and scope data, then decides whether the CVE path is usable, patched, not applicable, or needs more recon.
## Trigger
```text
cve_candidate_list_ready
```
## Feedback Gates