API

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.

  • Who it's forFor developers of inventory, CMDB or vulnerability management tools.
  • PlanFree account; more volume on the plans
  • Timeabout 20 min

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

  1. 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'
  2. 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
  3. 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.

  4. 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.

  5. 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"
  6. 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"

Something went wrong?

affected_versions came back emptyThe CNA did not publish a version range. Show it as "affects the family; version not confirmable" and track it with /changes: the range may arrive later.
/changes refused the dateUse ISO-8601 with the time zone (UTC's Z, for example) and a date up to 30 days back.
The batch went over the limitEach plan has a number of IDs per batch, and each ID counts toward the daily limit. Split the list into smaller batches.

Frequently asked questions

Does Vexday decide for me whether my version is vulnerable?

In the API, no: it returns the record's range, and the comparison is up to your system. In the dashboard, the inventory does that math, and alerts can filter by version.

Where does the version range come from?

From the official CVE record, published by the CNA, the organization that assigns the ID. version_type says how to compare.

How many IDs fit in a /cve/batch?

The number of IDs per batch depends on the plan and is on the pricing page.

Keep going