PermitANY
SecurityPrompt

CVE Vulnerability Prioritization

Paste a list of CVEs or vulnerability scan results and get a prioritized remediation plan based on your network context, exploitability, and actual risk — not just CVSS score.

40 copies
ChatGPTClaudeGemini

Customize variables

Brief description of the systems and their exposure

Paste CVE IDs with CVSS scores, or raw output from Nessus/Qualys/OpenVAS

Any constraints that affect remediation (patch windows, team size, vendor support)

Tips for better results

  • ·Paste the full scanner output — even low-CVSS findings provide context about the attack surface
  • ·Mention if you have WAF, IPS, or network segmentation — these are compensating controls
  • ·Ask follow-up questions about specific CVEs you are unsure about
  • ·For Cisco CVEs: reference cisco.com/go/psirt for official advisories and fixed versions

Prompt preview

○ ENVIRONMENT○ CVE_LIST○ CONSTRAINTS
You are a senior security engineer conducting vulnerability risk prioritization.

Environment: [Your environment]
Constraints: [Constraints / context]

Vulnerabilities to prioritize:
```
[CVE list or scan results]
```

Do NOT simply sort by CVSS score. Instead, provide context-aware prioritization:

1. PRIORITY 1 — Patch immediately (exploitable remotely, public exploit exists, high impact)
2. PRIORITY 2 — Patch in next maintenance window (high CVSS but mitigating controls reduce risk)
3. PRIORITY 3 — Schedule for next quarter (requires local access, limited blast radius)
4. ACCEPT — Document and monitor (too low risk to justify change risk)

For each CVE:
- Current risk level IN THIS ENVIRONMENT (not just generic CVSS)
- Whether a public exploit exists (known exploited in the wild)
- Compensating controls that reduce risk
- Specific remediation steps (patch version, workaround, or config change)

End with a remediation roadmap that fits within the stated constraints.

Tags

vulnerabilitycvecvssremediationriskpatching