The release's finding groups, one per CVE
const url = 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/finding-groups?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/finding-groups?include=resolved&limit=50' \ --header 'Authorization: Bearer <token>'A finding group is one problem: a CVE, or an advisory without a CVE, however many advisories (members) and components it has. Most urgent first: known exploited, then CVSS, then EPSS, then key. Groups resolved by VEX (not_affected, fixed) are left out unless include=resolved. Matching runs in the worker, so a new upload shows its groups shortly after.
The group’s vex_status is the statement on the CVE, else the members’ own statements combined; null means open. statements_differ: a member’s own statement differs from the CVE’s (the CVE’s decides). conflict is null unless another advisory with the CVE names a component a member matched but excludes its version: then it lists, per component, who says affected and who says not affected (with the version that fixes it, when the advisory has one). A conflict never resolves a group.
A page at a time (up to 200 groups, 50 by default): while more is true, ask again with after
set to next.
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 groups VEX marked not_affected or fixed
The next of the previous page
Responses
Section titled “Responses”A page of finding groups
object
One problem in a release: a CVE, or an advisory without a CVE, however many advisories (members) and components bring it in.
object
The CVE, or “source:id” (e.g. “osv:GO-2024-1”) for an advisory without one
The group’s finding ref, e.g. Gateway/rev-b@1.4.0:CVE-2024-1234 (GET /v1/orgs/{org}/finding-refs resolves it). Derived from the current product, variant and version names: it changes when one is renamed.
Null for an advisory without a CVE
The best-ranked member (vendor CSAF, coordinator CSAF, OSV, then NVD); the group’s first member
object
The NVD record’s title if it is a member, else the first member’s
The highest severity across the members (CRITICAL, HIGH, MEDIUM, LOW); absent when none
Highest CVSS base score across the members
The CVE is in CISA’s KEV catalog, or on ENISA’s exploited list from a source other than CISA
EPSS probability of the CVE (0-1)
The EUVD IDs of the CVE, sorted; empty when ENISA has none or this installation doesn’t sync the EUVD
CSAF advisories of vendors and coordinators that name the CVE, as on a vulnerability’s vendor_advisories; empty for a group without a CVE or when no provider this installation syncs has one. A member that is a CSAF record is one of them (its url is the advisory’s page).
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
The earliest member’s first match in this release, never before the SBOM that brings it in
A member’s own statement differs from the statement on the CVE (the CVE’s decides). Not a conflict.
The component occurrences the members matched
object
How the best-ranked member that matched it did
IDs of the advisories that matched it
object
object
object
object
How the advisory names the component
The version the advisory says fixes it; null when its data has none
The after of the next page; absent on the last. Opaque
More groups follow next
Example
{ "items": [ { "primary": { "source": "osv" }, "vendor_advisories": [ { "publisher": "vendor" } ], "vex_status": "not_affected", "members": [ { "source": "osv", "vex_status": "not_affected", "matched_via": [ "purl" ] } ], "components": [ { "matched_via": "purl" } ], "conflict": { "components": [ { "affected_by": [ { "source": "osv", "matched_via": "purl" } ], "not_affected_by": [ { "source": "osv", "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