mlab docs

Getting Started

Search, filter and fetch CVEs, feeds and exports from the vuln.mlab.sh API.

Everything here is a plain GET against https://vuln.mlab.sh, with no key. CORS is open, so it works from a browser too.

curl "https://vuln.mlab.sh/api/v1/cve?q=openssl&severity=HIGH&limit=10&page=0"

Every word of q must appear in the description (any order, case-insensitive), and a word that is a CVE id also matches that CVE. Filters combine:

ParameterMeaning
qKeywords, a CVE id, or a package coordinate (see below)
exact=1Match q as one literal phrase
severityCRITICAL, HIGH, MEDIUM, LOW; HIGH+ means high or worse
minSeverityThis severity or worse
minCvssMinimum CVSS base score
kevOnly=1Only CVEs in the CISA KEV catalogue
cweA weakness, for example CWE-79
cpeA CPE 2.3 name; a versioned CPE is matched against the NVD version ranges
dateStart, dateEndPublished between (YYYY-MM-DD), at most 366 days apart
sortDefault: newest first with known-exploited matches promoted on page 0; recent; severity
page, limit0-based page, up to 100 results per page
# Known-exploited, critical, this year
curl "https://vuln.mlab.sh/api/v1/cve?kevOnly=1&severity=CRITICAL&dateStart=2026-01-01&dateEnd=2026-12-31"

# Everything affecting a precise product version (NVD configurations)
curl "https://vuln.mlab.sh/api/v1/cve?cpe=cpe:2.3:a:apache:log4j:2.14.1:*:*:*:*:*:*:*"

By package

Give q a package coordinate to get the CVEs affecting it, from the OSV data: a purl, or <ecosystem>/<name>[@version].

curl "https://vuln.mlab.sh/api/v1/cve?q=pkg:npm/[email protected]"
curl "https://vuln.mlab.sh/api/v1/cve?q=pypi/[email protected]"

Ecosystems: npm, pypi, cargo, go, maven, nuget, composer, gem, pub, hex. This mode returns at most 60 CVEs and ignores the other parameters. To check a whole lockfile, use the SBOM scan.

A single CVE

curl "https://vuln.mlab.sh/api/v1/cve/CVE-2021-44228"

The record carries CVSS (score, severity, vector and its breakdown), EPSS score and percentile, in_kev with the CISA dates, in_eu_kev, the EUVD id, CWE weaknesses, references with their tags, the affected products and NVD configuration ranges (cpe_matches), and a risk_score: 100 for a known-exploited CVE, otherwise CVSS weighted by the EPSS percentile.

More about the same CVE:

# Package advisories (GHSA, RUSTSEC, PYSEC, GO) with affected and fixed versions
curl "https://vuln.mlab.sh/api/v1/cve/CVE-2021-44228/osv"

# National CERT advisories that cite it
curl "https://vuln.mlab.sh/api/v1/advisories?cve=CVE-2021-44228"

# Public exploits and PoCs (looked up live: 3 per hour per IP on a cache miss)
curl "https://vuln.mlab.sh/api/v1/cve/CVE-2021-44228/pocs"

Latest CVEs

The 40 newest CVEs of the last 7 days, enriched:

curl "https://vuln.mlab.sh/api/v1/cve/latest"

Bulk dump

Every scored CVE published in a window of at most 31 days, above a minimum CVSS, sorted by score (up to 10 000):

curl "https://vuln.mlab.sh/api/v1/cve/dump?dateStart=2026-09-01&dateEnd=2026-09-30&minCvss=7.5"

Dump items are not enriched (no EPSS or KEV). The endpoint allows 12 calls per hour per IP, 15 seconds apart, and answers 429 with Retry-After beyond that. For a longer period, request consecutive ranges.

Feeds and exports

# RSS 2.0: the 20 latest CVEs (also at /feed)
curl "https://vuln.mlab.sh/rss"

# RSS of a search: subscribe to exactly what you follow
curl "https://vuln.mlab.sh/rss?q=fortinet&kevOnly=1"

# CSV of a search (up to 100 rows)
curl -OJ "https://vuln.mlab.sh/export/csv?q=log4j"

A feed with search parameters returns up to 50 matching CVEs, newest first. For alerts tied to your account (inbox, webhook, per-watch RSS), see Watchlists and alerts.

Statistics and health

curl "https://vuln.mlab.sh/api/v1/stats"                          # corpus counts, KEV, EPSS
curl "https://vuln.mlab.sh/api/v1/sources"                        # sync state of each source
curl "https://vuln.mlab.sh/api/v1/vendor/microsoft/months?year=2025"  # CVEs per month

Errors

The v1 JSON endpoints answer 200 with { "error": "message" } in place of the documented shape, so test for the error key. Only /api/v1/cve/dump uses 429, and an unknown path returns an HTML 404.

Need a blocking, package-scoped gate rather than keyword search? See OSV integration or the SBOM scan.

On this page