How to Read a CVE Advisory: CVSS vs EPSS vs KEV
A practical guide to CVE records — identifiers, CVSS severity, EPSS exploit probability, and CISA KEV — and why proof on your stack beats chasing every Critical score.
New CVE drops at 9.8. Your dependency tree includes three packages with similar names. Panic is optional; reading the record is not.
Opening a CVE advisory can feel like drinking from a firehose: scores, vectors, CPEs, references, and conflicting vendor notes. This post teaches how to read a record — not how to clone NVD. Hub: Learn → CVE.
The four signals
CVE ID
CVE-YYYY-NNNNN is a shared name for a disclosed vulnerability. It lets vendors and teams point at the same issue. It does not mean your deployment is exploitable.
Glossary: CVE.
CVSS
The Common Vulnerability Scoring System produces a 0–10 base score from metrics like attack vector, privileges required, and CIA impact. A Critical score means severe in the abstract. Environmental factors — exposure, auth, compensating controls — still dominate your backlog order.
Glossary: CVSS.
EPSS
Exploit Prediction Scoring System estimates how likely a CVE is to be exploited in the wild in a near-term window. Use it as a prioritization hint, not as destiny.
KEV
CISA’s Known Exploited Vulnerabilities catalog lists CVEs observed as exploited. If you run the affected software on reachable systems, treat KEV as urgent.
A five-question reading checklist
- What product and versions are listed? Do we actually run them?
- What is the attack pre-condition (auth, user interaction, network path)?
- What do CVSS / EPSS / KEV say in combination — not CVSS alone?
- Is there a vendor fix or mitigation we can apply without guessing?
- Can we prove impact in our environment (or safely conclude we are not exposed)?
Why PandaONE does not ship a fake CVE search here
Some vendors host searchable mirrors of hundreds of thousands of CVEs. Our static marketing site will not pretend to. Learn/cve teaches literacy; vulnerability class guides and AI VAPT focus on proof on your apps. Full CVE search is noted as coming — without a decoy UI.
Classic case study: CVE-2021-44228 Log4Shell.