Vulnerabilities the release's SBOM components are affected by
const url = 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/vulnerabilities?include=resolved&limit=50';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/vulnerabilities?include=resolved&limit=50' \ --header 'Authorization: Bearer <token>'The items are advisories: one per OSV, NVD or CSAF record, so one CVE can appear several times. A release’s number of problems is the number of distinct groups (the keys in each item’s groups), which finding-groups lists one by one.
Most urgent first: known exploited (CISA KEV, or ENISA’s list from a source other than CISA), then CVSS, then EPSS. Matching runs in the worker, so a new upload shows its vulnerabilities shortly after, not in the upload response. Findings resolved by VEX (not_affected, fixed) are left out unless include=resolved.
A page at a time (up to 200 advisories, 50 by default): while more is true, ask again with
after set to next. A page that is cut keeps every component of its advisories.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Query Parameters
Section titled “Query Parameters”Resolved: also list findings VEX marked not_affected or fixed
The next of the previous page
Responses
Section titled “Responses”A page of vulnerabilities
object
An advisory the release is affected by. Several advisories can name one CVE; a release’s number of problems is the number of distinct groups (finding-groups lists them).
object
The keys of the finding groups the advisory is in (its CVEs, or source:id for an advisory without one)
One of the advisory’s groups has sources that disagree (see finding-groups)
Osv: matched by package URL; nvd: matched by CPE; csaf: a provider’s CSAF advisory, matched by its product’s package URL or CPE
Advisory or record ID, e.g. “DSA-5343-1”, “GHSA-…”, “CVE-2023-0286”
NVD severity of the worst CVE (CRITICAL
Highest NVD CVSS base score of the CVEs
One of the CVEs is in CISA’s KEV catalog, or on ENISA’s exploited list from a source other than CISA
Highest EPSS probability of the CVEs (0-1)
The EUVD IDs (ENISA’s EU Vulnerability Database, e.g. EUVD-2025-4893) of the record’s CVEs, sorted; empty when ENISA has none or this installation doesn’t sync the EUVD.
CSAF advisories of vendors and coordinators (BSI, CERT@VDE, CISA, Siemens, …) that name one of the finding’s CVEs, by ID; withdrawn ones are left out. Empty when no provider this installation syncs has one.
object
Record ID,
The provider’s advisory ID, e.g. “SSA-104023”
The provider, e.g. “siemens”, “bsi-wid”, “cisa-ics”
How the provider is shown, e.g. “Siemens ProductCERT”
The provider’s category
The advisory’s page at the provider, or its CSAF document
Products the advisory says are fixed in a version, or have a vendor fix, for the finding’s CVEs (at most 20)
object
The version that fixes the product
Where the vendor’s fix is
Other records that matched the same components for some of this finding’s CVEs, which this finding supersedes: one finding per component and CVE set, ranked a vendor’s CSAF advisory, a coordinator’s, OSV, then NVD. They are no findings of their own. Empty when there are none.
object
A CSAF advisory’s page; absent for OSV and NVD records
First matched to this release, never before the SBOM that brings it in
object
Purl: OSV; cpe: NVD (curated list or the SBOM’s CPE); csaf_purl, csaf_cpe: a CSAF advisory’s product, by package URL or CPE; org_cpe: NVD or a CSAF advisory through the organization’s own CPE mapping; org_csaf: a CSAF advisory through the organization’s own CSAF product mapping
The after of the next page; absent on the last. Opaque
More vulnerabilities follow next
Example
{ "items": [ { "source": "osv", "vendor_advisories": [ { "publisher": "vendor" } ], "also_in": [ { "source": "osv" } ], "vex_status": "not_affected", "components": [ { "matched_via": "purl" } ] } ]}Request.invalid (params.field include, limit or after)
No such object in this organization, no such organization, or the caller does not belong to it
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1