Everything Deepinfo knows about one CVE, in one call.
Pass a CVE ID. Get back the full enriched record: CVSS, EPSS, CISA KEV, CWE, affected products, references, and Deepinfo-specific risk scoring.
The full enrichment surface, for one CVE.
The Vulnerability Detail API is the per-record version of Vulnerability Search. Pass one CVE ID and the API returns the full enriched record: published date, CVSS metric, EPSS exploit-prediction score, CISA KEV active-exploitation flag, CWE classification, affected vendor and product set, references, and Deepinfo-specific risk scoring.
Use this when you have a specific CVE ID and need the full context behind a finding instead of running a corpus filter. The response is shaped to be self-contained: every field that Search exposes for filtering is present here for direct read.
Every CVE returned by Vulnerability Finder against a target carries the ID needed to call Vulnerability Detail directly. The two APIs compose cleanly.
One endpoint, one required parameter.
Endpoint:
GET https://api.deepinfo.com/v1/discovery/vulnerability-detail?cve={cve}Parameters:
Authentication is by API token in the request header. See docs.deepinfo.com for the full request reference.
See what the API returns.
Real response structure for the Everything Deepinfo knows about one CVE, in one call endpoint. Field coverage may vary based on query parameters and data availability.
{
"id": "CVE-2026-1842",
"source_identifier": "[email protected]",
"published": "2026-04-08T00:00:00Z",
"last_modified": "2026-04-22T18:14:00Z",
"status": "Modified",
"summary": "Remote code execution in Example Vendor Product before 4.2.",
"enrichment": {
"cpe": [{"vendor": "example-vendor", "product": "example-product", "version_lt": "4.2"}],
"vdeep_metric": {
"cvss_data": {"base_score": 9.8, "base_severity": "CRITICAL"},
"deepinfo_risk_score": 94
},
"epss_score": {"epss": 0.94, "percentile": 0.999},
"cisa_kev": {"is_listed": true, "date_added": "2026-04-12", "due_date": "2026-05-03"},
"cwe": [{"id": "CWE-94", "name": "Improper Control of Generation of Code"}]
},
"references": ["https://example-vendor.com/security/CVE-2026-1842"]
}Sample response shown. Real responses depend on query parameters, data availability, and API version. Talk to us for full schema documentation.
Workflows this API plugs into directly.
Vulnerability Management
Pull the full record on any CVE in your queue without composing per-source calls.
Read the use caseIncident Investigation and Response
Look up CVEs surfaced in incident telemetry with one call.
Read the use caseCompliance and Audit Readiness
Map CVEs to CWE classifications and affected-product sets for evidence exports.
Read the use case“EPSS, CISA KEV, and CWE all in the same record means we don't normalize across three NVD-adjacent sources anymore. Risk scoring is consistent because the input data is consistent.”
Pull the full CVE record, or batch lookup your queue.
We'll set up token access and answer schema questions on a call.