sodcalculator

10 Tech How-To

How to Prioritize CVE Fixes Across Your Software Inventory

Guide 10-49829 · Updated · Step by step

This guide walks you through a practical, repeatable process for deciding which Common Vulnerabilities and Exposures (CVEs) in your software inventory to fix first. You’ll learn how to gather your asset data, score each vulnerability using context beyond the raw CVSS number, and turn that into a prioritized action list your team can execute.

What You’ll Need

  • A current inventory of software and versions (from a CMDB, asset management tool, or manual list).
  • Access to vulnerability scan results or a CVE feed (e.g., NVD, vendor advisories, or a commercial scanner).
  • A spreadsheet or a simple project management tool (like Trello, Jira, or even a shared sheet) to track decisions.
  • Knowledge of which systems are internet-facing, contain sensitive data, or are critical to business operations.
  • An understanding of your organization’s risk tolerance and change management process (for scheduling patches).

Step-by-Step

  1. Build a complete software inventory. List every application, operating system, library, and firmware version you run. Include the vendor, product name, and exact version. If you don’t have this yet, use your existing asset management tools or run a discovery scan. Without a complete inventory, you’ll miss CVEs that matter.
  2. Map CVEs to your inventory. For each software item, find the CVEs that affect that exact version. Use the CPE (Common Platform Enumeration) identifiers from the NVD or your scanner’s output. Match the CVE’s affected versions against your installed versions. This step is often automated by vulnerability scanners, but if you’re doing it manually, create a mapping table.
  3. Record the base CVSS score for each CVE. The CVSS (Common Vulnerability Scoring System) base score (0-10) gives a rough severity. Note it, but don’t stop there—it only reflects the intrinsic properties of the vulnerability, not your environment.
  4. Assess environmental context. For each CVE, determine:
    • Is the affected system exposed to the internet? (If yes, higher priority.)
    • Does it process sensitive data (PII, financial, health)? (If yes, higher priority.)
    • Is it a critical system (domain controller, ERP, production server)? (If yes, higher priority.)
    • Is there a known exploit available? (Check exploit-db, Metasploit, or vendor advisories. If yes, higher priority.)
  5. Calculate a priority score. Use a simple formula: Priority = (CVSS base score × 2) + (Exploit availability ? 3 : 0) + (Internet-facing ? 2 : 0) + (Sensitive data ? 2 : 0) + (Critical system ? 1 : 0). This gives a score from 0 to 27. You can adjust the weights to fit your risk appetite, but the key is to make it repeatable.
  6. Sort and group by priority. List all CVEs with their priority scores in descending order. Group them into tiers: Critical (score ≥ 20), High (15-19), Medium (10-14), Low (<10). This grouping helps you communicate with stakeholders.
  7. Consider exploitability and impact. For the top-tier items, look deeper: Is the attack vector network-based (AV:N) or local (AV:L)? Does it allow remote code execution (RCE) or just information disclosure? A CVE with a lower CVSS but active exploitation may outrank a higher CVSS with no exploit.
  8. Check for mitigating controls. Before adding a CVE to your fix list, see if existing security controls reduce the risk. For example, a firewall blocks the affected port, or the vulnerable component isn’t actually used. If a mitigation is in place, you can lower the priority or defer the fix.
  9. Plan the remediation. For each CVE in your top tiers, decide the action: patch, apply a workaround, or accept the risk (with documentation). Schedule patches according to your change windows, but aim to fix critical items within days, not weeks. For lower tiers, batch them into regular maintenance cycles.
  10. Track and review. Log every decision: the CVE, the score, the rationale, and the action. After patching, verify the fix (e.g., re-scan) and close the ticket. Review your prioritization process quarterly to adjust weights as your environment changes.

Common Mistakes

  • Relying solely on CVSS base scores. A 10.0 CVE on an isolated test server is less urgent than a 7.5 on your public-facing web app.
  • Ignoring exploit availability. If a working exploit is public, that CVE jumps the queue even if the CVSS is moderate.
  • Not updating your inventory. If you don’t know what’s installed, you can’t know what’s vulnerable. New software appears all the time.
  • Treating all systems equally. A vulnerability on a domain controller is far more damaging than one on a non-critical reporting server.
  • Forgetting about dependencies. A vulnerable library inside an application may be missed if you only scan top-level software.
  • Delaying patches for fear of breakage. While testing is good, indefinite deferral leaves you exposed. Use a staging environment to test quickly.

Tips

  • Automate the inventory and mapping steps with tools like vulnerability scanners, but always validate the output—false positives are common.
  • Use the EPSS (Exploit Prediction Scoring System) as an additional signal. It estimates the likelihood of exploitation in the wild.
  • Keep a “risk register” for accepted risks. If you decide not to fix a CVE, document why and set a review date.
  • Communicate priorities in business terms: “This CVE could allow an attacker to steal customer data” is more effective than “CVSS 9.8.”
  • Create a patching SLA: critical CVEs within 7 days, high within 30, medium within 90, low by next major release.
  • When a vendor releases an out-of-band patch, treat it as urgent—it usually means active exploitation.

Troubleshooting

What if you have too many CVEs to handle? Focus on the top 10% by your priority score first. That group usually represents the majority of risk. Defer the rest to a later cycle.

What if a patch breaks an application? Before patching, ensure you have a rollback plan. Test on a non-production system first. If a break occurs, revert and search for a workaround or a newer patch.

What if you lack a complete inventory? Start with your internet-facing systems—they are the highest risk. Then move to internal servers, and finally endpoints. Use network scanning tools to discover unmanaged devices.

What if a CVE affects a component you can’t patch (e.g., end-of-life software)? Implement compensating controls: isolate the system, restrict network access, or apply vendor workarounds. If possible, plan to decommission or replace the software.

What if your scanner reports a CVE but the vendor says it’s not applicable? Investigate the CPE match. Sometimes the scanner misidentifies the version. Verify the exact version and consult the vendor’s advisory.

Frequently Asked Questions

Q: Should I always fix the highest CVSS score first?
A: No. CVSS is a starting point, but environmental factors like exposure, exploitability, and system criticality often matter more. A lower CVSS with active exploits can be more urgent.

Q: How often should I re-prioritize?
A: At least weekly, and immediately after any major vulnerability disclosure (e.g., Log4Shell) or when new exploits appear. Your inventory changes, and new CVEs are published daily.

Q: What is EPSS and should I use it?
A: EPSS is a score (0-1) predicting the probability that a CVE will be exploited in the next 30 days. It’s a useful complement to CVSS, but don’t rely on it alone—some critical systems warrant fixing regardless of low exploit probability.

Q: Can I skip patching if I have a firewall or WAF?
A: Only if the control fully mitigates the vulnerability. For example, if the CVE is for a service that’s not accessible from the internet and you have strict egress filtering, you might defer. But document the decision and re-evaluate regularly.

Q: How do I handle CVEs in open-source libraries?
A: Use software composition analysis (SCA) tools to detect vulnerable libraries. Prioritize them the same way, but also check if the library is actually called in your code—if not, you can deprioritize.

Q: What if a patch isn’t available yet?
A: Look for vendor workarounds or mitigations. If none exist, increase monitoring, restrict access, and isolate the system if possible. Track the vendor’s release timeline and re-evaluate when the patch drops.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →