EPSS scores are published daily, free of charge, with no registration required. There are three ways to access the data:
The EPSS API is designed for lookup, not bulk access. The intended use case is querying the current score for one CVE or a small batch (e.g. enriching an incoming ticket, checking a specific vulnerability's score from a script, or integrating EPSS into a tool that surfaces scores on demand). It should not be used for bulk downloads or to keep a local copy of all scores in sync; the daily CSV or the GitHub repository is the right mechanism for that.
Beyond basic lookup, the API supports a few additional patterns. You can pin a request to a past date to retrieve what the score was on that day, which is useful when reconstructing a prioritization decision. You can request a 30-day score history for a single CVE, returning the daily score and percentile for each of the last 30 days — useful for understanding how a score has moved in response to emerging signals. Basic filtering by score or percentile range is also available, as is partial CVE ID search.
Full parameter reference, response format, and examples: api.first.org/epss. FIRST.org maintains the EPSS API interface. Please note the "v1" in the URL is a reference to the API version, not the EPSS version.
A single stable URL always points to the current day's complete file:
https://epss.empiricalsecurity.com/epss_scores-current.csv.gz
The file is a gzip-compressed CSV containing three fields for every scored vulnerability:
cve — the CVE identifierepss — the EPSS score, a probability between 0 and 1percentile — the proportion of all scored vulnerabilities with the same score or lowerThe URL does not change; fetching it always returns today's scores. Note that the URL redirects, so use -L with curl:
curl -sL https://epss.empiricalsecurity.com/epss_scores-current.csv.gz | gunzip -c 2>/dev/null | head -1
For most batch workflows — loading scores into a database, joining against an asset inventory, feeding a dashboard — pulling this file once per day is more efficient than querying the API per CVE.
The full daily archive of score files is available at:
github.com/empiricalsec/epss_scores
Each file corresponds to one day's scored population in the same three-field format as the daily CSV. Files are available back to 2021-04-14.
If you are building a time series or doing historical analysis, note that each model version produced a score shift on the date it started publishing. A time series that crosses one of these boundaries reflects a change in methodology, not a change in the vulnerability itself.
#) stating the model version and publish dateEPSS is maintained by the EPSS Special Interest Group at FIRST. Scores are generated by Empirical Security and published freely to the community.