Empirical Security CVEs API
Retrieve CVE detail, scores, malware hashes and history.
Empirical Security CVEs API is one of 3 APIs that Empirical Security publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include CVEs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 6 operations across 6 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.
Requests are made against a single base URL, https://app.empiricalsecurity.com/api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Empirical Security CVEs API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 1 scope.
By default, every request must be authenticated.
oauth2— OAuth 2.0 client credentials flow via FusionAuth. Exchange client ID/secret (HTTP Basic) for a one-hour JWT access token, then send it as a Bearer token.
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.
Retrieve CVE detail, scores, malware hashes and history.
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Cve (6 properties), Score (3 properties), MalwareHash (3 properties), ScoreHistory (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Empirical Security 2
Other APIs Empirical Security publishes across the network.