Skip to main content
PATCH
/
project
/
{projectId}
/
results
/
{vulnerabilityId}
Update a vulnerability of a project
curl --request PATCH \
  --url https://us.cybedefend.com/project/{projectId}/results/{vulnerabilityId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "status": "to_verify",
  "priority": "critical_urgent",
  "comment": "<string>",
  "userId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
'
{
  "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "vulnerabilityId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "vulnerability": "<unknown>"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
projectId
string<uuid>
required
​
vulnerabilityId
string<uuid>
required

Body

application/json
​
status
enum<string>

Status of the vulnerability

Available options:
to_verify,
not_exploitable,
proposed_not_exploitable,
resolved,
confirmed,
ignored
​
priority
enum<string>

Priority level

Available options:
critical_urgent,
urgent,
normal,
low,
very_low
​
comment
string

Comment about the vulnerability (max 512 chars)

Maximum string length: 512
​
userId
string<uuid>

User unique identifier that updates the vulnerability

Response

Updated vulnerability

​
projectId
string<uuid>
required

Project unique identifier

​
vulnerabilityId
string<uuid>
required

Vulnerability unique identifier

​
vulnerability
required

Vulnerability object with a discriminator for SAST, IAC, or SCA