How to tell from the API whether the installed version is affected by a CVE
Use the affected_versions field to decide whether your version is in the vulnerable range, and /changes with /cve/batch to keep your database current without downloading everything again.
What you need
- An API key: the getting-started guide shows how to create one.
- The list of products and versions you want to check.
Account limits: free, 50 per day and 10 per minute · SOC, 5,000 per day and 60 per minute · MSSP, 20,000 per day and 120 per minute.
Step by step
Read the CVE's affected_versions
Each item carries the vendor, the product, the range base (version), the exclusive (less_than) or inclusive (less_or_equal) upper bound, the status and the version_type, which says how to compare.
curl -s -H "Authorization: Bearer vx_live_SUA_CHAVE" \ "https://api.vexday.io/api/v1/cve/CVE-2024-3400" | jq '.data.affected_versions'
Compare as versions, not as text
Use a comparator that respects version_type, such as Python's packaging.version for semver. In alphabetical order a lower version can look higher; git and custom need their own handling.
"2.4.9" > "2.4.49" # verdadeiro como texto, falso como versão
Respect the bounds and the status
less_than excludes the bound and less_or_equal includes it: getting this wrong fails exactly at the boundary version. A range with status unaffected is the CNA saying it is not vulnerable.
Treat an empty range as missing data
With no affected_versions, the CNA did not publish versions: the CVE affects the product family, and your version cannot be confirmed. Show the gap instead of concluding it is not affected.
Fetch only what changed
/changes lists the CVEs, incidents and victims that changed since a date, up to 30 days back. With truncated, repeat the call with the next_since from the response.
curl -s -H "Authorization: Bearer vx_live_SUA_CHAVE" \ "https://api.vexday.io/api/v1/changes?since=2026-11-01T00:00:00Z"
Fetch the detail in bulk
/cve/batch returns several CVEs in one call. Each ID counts as one request against the daily limit, and unknown ones come back in not_found, with no error.
curl -s -X POST -H "Authorization: Bearer vx_live_SUA_CHAVE" -H "Content-Type: application/json" \ -d '{"ids": ["CVE-2024-3400", "CVE-2021-44228"]}' "https://api.vexday.io/api/v1/cve/batch"