# Dismiss or reopen a vulnerability alert

> Dismiss a vulnerability alert (state dismissed, with a reason: fix_started, no_bandwidth, tolerable_risk, inaccurate or not_used, and an optional comment) or reopen it (state open).

<div class="g1t-endpoint"><span class="g1t-method" data-method="patch">PATCH</span><code>/repos/{owner}/{name}/vulnerability-alerts/{id}</code></div>

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`security`](/reference/mcp/#security) with `action` `update_vulnerability_alert`, and the same inputs
- **Scope:** An access token needs [`security:write`](/guides/authentication/#scopes).

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `owner` | string | Yes | The workspace that owns the repository. |
| `name` | string | Yes | The repository's name. |
| `id` | string | Yes | The alert's id: vul_… |

## Body parameters

Send a JSON object. Names are `snake_case`, as in responses; the `camelCase` spelling is accepted too.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `state` | string | Yes | dismissed, with a reason, or open to reopen. One of `open`, `dismissed`. |
| `reason` | string | No | Why it is dismissed. One of `fix_started`, `no_bandwidth`, `tolerable_risk`, `inaccurate`, `not_used`. |
| `comment` | string | No | Why, in a sentence; kept with the alert. At most 500 characters. |

## Example request

```sh
curl -X PATCH https://api.g1t.sh/repos/flagon-io/hello/vulnerability-alerts/vul_01kp4b8c3d4e5f6g7h8j9k0m1n \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "dismissed",
    "reason": "tolerable_risk",
    "comment": "Only the build uses it."
  }'
```

## Example response

A successful request answers `200` with:

```json
{
  "id": "vul_01kp4b8c3d4e5f6g7h8j9k0m1n",
  "repo_id": "rep_01kp0a1b2c3d4e5f6g7h8j9k0m",
  "ecosystem": "npm",
  "package": "lodash",
  "version": "4.17.20",
  "manifest": "package-lock.json",
  "advisory": "GHSA-35jh-r3h4-6jhm",
  "osv_id": "GHSA-35jh-r3h4-6jhm",
  "summary": "Command Injection in lodash",
  "severity": "high",
  "fixed_version": "4.17.21",
  "status": "dismissed",
  "issue": null,
  "found_at": "2026-10-06T09:14:02.118Z",
  "fixed_at": null,
  "state": "dismissed",
  "dismissed_by": "syntaqx",
  "dismissed_reason": "tolerable_risk",
  "dismissed_comment": "Only the build uses it.",
  "dismissed_at": "2026-10-06T09:20:41.502Z",
  "update": null
}
```

## Errors

A failed request answers with one of these statuses and a body like `{"error": {"code": "not_found", "message": "Repository not found."}}`. See [errors](/reference/api/#errors).

| Status | Code | When |
| --- | --- | --- |
| 401 | `unauthenticated` | A token is required, or the one sent is not valid. |
| 403 | `forbidden` | The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository. |
| 404 | `not_found` | It does not exist, or you cannot see it. |
| 409 | `conflict` | The request conflicts with the current state. |
| 422 | `invalid` | The input is not valid. `message` says which field and why. |