← CRA Glossary
CVD & Vulnerability Management

Exploit Prediction Scoring System (EPSS)

The Exploit Prediction Scoring System (EPSS) is a data-driven model maintained by FIRST that estimates the probability that a given CVE will be exploited in the wild within the next 30 days. EPSS complements CVSS by adding exploitation likelihood to severity, enabling more effective vulnerability prioritisation.

The Exploit Prediction Scoring System (EPSS) is a data-driven model maintained by FIRST that estimates the probability that a given CVE will be exploited in the wild within the next 30 days. EPSS complements CVSS by adding exploitation likelihood to severity, enabling more effective vulnerability prioritisation.

CVD & Vulnerability Management

Last updated 19 July 2026

What Is EPSS?

The Exploit Prediction Scoring System (EPSS) is a probabilistic model, maintained by FIRST (Forum of Incident Response and Security Teams), that estimates the likelihood that a specific CVE will be actively exploited in the wild within the next 30 days. The model is trained on a large dataset of CVE characteristics and observed exploitation telemetry from multiple sources, including Shadowserver, GreyNoise, and commercial threat intelligence providers. EPSS scores are expressed as a percentage probability (0.0 to 1.0) and are updated daily. A CVE with an EPSS score of 0.95 has a 95% estimated probability of being exploited within 30 days; a CVE with a score of 0.01 is very unlikely to be exploited in that window.

CRA reference:Annex I

EPSS vs CVSS: Complementary Frameworks

CVSS and EPSS answer different questions. CVSS answers: 'If this vulnerability is exploited, how bad could it be?' - it measures severity based on technical characteristics. EPSS answers: 'How likely is it that this vulnerability will be exploited in the next 30 days?' - it measures exploitation probability based on observed threat intelligence.

Using CVSS alone for prioritisation leads to over-prioritisation of theoretical risks: only approximately 5% of all CVEs are ever exploited in the wild. A manufacturer prioritising solely by CVSS score invests remediation effort in many vulnerabilities that pose minimal real-world risk. EPSS dramatically sharpens prioritisation by surfacing the small subset of CVEs that attract active attacker attention. Combined, CVSS (severity) and EPSS (likelihood) provide a risk-informed prioritisation framework - the foundation of risk-based vulnerability management.

CRA reference:Annex I

Using EPSS in CRA-Compliant Vulnerability Handling

For manufacturers subject to CRA obligations, EPSS provides a practical mechanism for demonstrating that vulnerability prioritisation is risk-informed rather than arbitrary. Specifically:

  • Triage prioritisation: EPSS can be used alongside CVSS to rank vulnerabilities - elevating lower-CVSS vulnerabilities that have high exploitation probability, and deprioritising high-CVSS vulnerabilities with negligible exploitation likelihood.
  • SLA adjustment: When an EPSS score spikes for a vulnerability affecting the product (for example, when exploitation tools are published), the manufacturer can escalate its remediation priority even before CISA KEV inclusion is confirmed.
  • Risk-based 'not affected' decisions: Using EPSS to justify why a very low-probability-of-exploitation CVE in a non-reachable code path is deprioritised provides a defensible, data-driven record for MSA review.
  • SBOM-based monitoring: Automated daily checks of EPSS scores for all CVEs affecting components in the product's SBOM enable proactive monitoring.
CRA reference:Annex I

Limitations and How to Interpret EPSS Scores

EPSS has important limitations that manufacturers should understand:

  • It measures population-level exploitation probability, not the specific risk to a given deployment. A CVE exploited in one environment will raise EPSS even if the manufacturer's specific product version is not the target.
  • Low EPSS does not mean no risk: A newly published critical vulnerability may have a low initial EPSS score simply because no exploitation data is yet available. EPSS scores for new CVEs typically rise rapidly if exploitation occurs.
  • EPSS v3.0+ is the current model: Earlier versions had significantly different score distributions. Manufacturers using historical EPSS data should verify which model version the scores were generated by.
  • EPSS does not replace CVSS: Severity matters independently of exploitation probability. A critical vulnerability that is not yet exploited should still be patched promptly, even if EPSS is temporarily low.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Where can manufacturers access EPSS scores?+

EPSS scores are freely available from FIRST at first.org/epss. The FIRST EPSS API provides bulk downloads and per-CVE lookups. EPSS data is also integrated into many vulnerability management platforms, SBOMs tools, and NVD-based feeds. CVD Portal integrates EPSS data into its SBOM vulnerability correlation feature, surfacing the exploitation probability for each matched CVE alongside its CVSS score.

At what EPSS threshold should a manufacturer escalate remediation priority?+

FIRST does not prescribe a specific threshold, and the appropriate threshold depends on the manufacturer's risk tolerance and product criticality. Common practices: treat any CVE with EPSS above 0.50 (50% exploitation probability) as high priority regardless of CVSS base score; use EPSS above 0.10 as a signal to review whether the normal remediation SLA is appropriate; flag any CVSS Critical + EPSS above 0.05 for expedited response. The CISA KEV catalogue provides a definitive trigger regardless of EPSS score for confirmed-exploited vulnerabilities.

How quickly do EPSS scores update when a new exploit is published?+

EPSS scores update daily. When exploit code is published or exploitation is observed in threat intelligence data, the EPSS model typically reflects this within 24–48 hours through a significant score increase. Manufacturers monitoring EPSS for their SBOM components should run daily checks rather than weekly, as the window between exploit publication and widespread exploitation is often very short for high-profile vulnerabilities.

Sector checklists covering Exploit Prediction Scoring System (EPSS)

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Exploit Prediction Scoring System (EPSS) fits into your complete CRA compliance programme.

View checklists →