> ## Documentation Index
> Fetch the complete documentation index at: https://docs.app.strix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update status or severity of multiple vulnerabilities

> Applies one status and/or severity change to up to 100 vulnerabilities in a single request. The server processes each vulnerability independently and reports per-vulnerability success or failure. Vulnerabilities that already have the requested values count as successful.



## OpenAPI

````yaml /openapi.json post /vulnerabilities/bulk-update
openapi: 3.1.0
info:
  title: Strix API
  version: 1.0.0
  description: >-
    Public REST API for the Strix autonomous penetration testing platform.
    Manage scans, vulnerabilities, assets, schedules, API tokens, and webhooks.
servers:
  - url: /api/v1
    description: Strix v1 API
security:
  - BearerAuth: []
tags:
  - name: Scans
    description: Launch, monitor, and manage security scans.
  - name: Vulnerabilities
    description: View and triage discovered vulnerabilities.
  - name: Assets
    description: Domains and repositories registered for scanning.
  - name: Schedules
    description: Recurring scan schedules (Pro plan).
  - name: Tokens
    description: Manage API tokens for authentication.
  - name: Webhooks
    description: Configure webhook subscriptions for real-time event notifications.
  - name: Organization
    description: Workspace configuration for the authenticated organization.
  - name: Members
    description: Manage organization members and roles.
  - name: Invitations
    description: List and revoke organization invitations.
  - name: PR Reviews
    description: Automated security review of pull requests.
  - name: Connectors
    description: Network connectors for scanning internal/private targets.
  - name: Knowledge
    description: >-
      Organization knowledge base: documents, policies, and repo profiles that
      steer the agent.
  - name: Uploads
    description: Upload source/code/documentation archives for whitebox scans.
  - name: Integrations
    description: Third-party integrations (GitLab, Bitbucket, ticketing).
  - name: Chat
    description: Conversational agent sessions.
  - name: Analytics
    description: Aggregate dashboard analytics.
  - name: Test Users
    description: >-
      Per-domain test accounts (with optional MFA) the agent authenticates as
      during scans.
  - name: License
    description: Self-hosted license state, entitlements, and aggregate usage.
  - name: Supply Chain
    description: >-
      SBOM inventory, supply-chain findings, scans, and policy for connected
      repositories.
  - name: CLI
    description: >-
      Device authorization endpoints that let the Strix CLI and coding agents
      sign in and receive an API token.
  - name: Billing
    description: Credit balance, agent-payable top-ups, and automatic top-up settings.
  - name: Workspaces
    description: List, create, and switch workspaces.
  - name: Asset Discovery
    description: >-
      Passive reconnaissance runs that map the organization's external attack
      surface, and the discovered-asset inventory they fill.
  - name: Run Logs
    description: Persisted engine logs and the diagnostics bundle of a self-hosted install.
paths:
  /vulnerabilities/bulk-update:
    post:
      tags:
        - Vulnerabilities
      summary: Update status or severity of multiple vulnerabilities
      description: >-
        Applies one status and/or severity change to up to 100 vulnerabilities
        in a single request. The server processes each vulnerability
        independently and reports per-vulnerability success or failure.
        Vulnerabilities that already have the requested values count as
        successful.
      operationId: bulkUpdateVulnerabilities
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BulkUpdateVulnerabilitiesRequest'
      responses:
        '200':
          description: Per-vulnerability update results.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BulkUpdateVulnerabilitiesResponse'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '500':
          $ref: '#/components/responses/InternalError'
      security:
        - BearerAuth:
            - vulnerabilities:write
components:
  schemas:
    BulkUpdateVulnerabilitiesRequest:
      type: object
      required:
        - vulnerability_ids
      description: >-
        Applies the same status and/or severity change to many vulnerabilities.
        Provide at least one of `status` or `severity`.
      properties:
        vulnerability_ids:
          type: array
          items:
            type: string
          minItems: 1
          maxItems: 100
          description: >-
            Vulnerability ids to update. The server removes duplicates. Maximum
            100 ids.
        status:
          $ref: '#/components/schemas/VulnerabilityStatus'
          description: New triage status for every listed finding.
        note:
          type: string
          description: Optional note when changing status.
        snoozed_until:
          type: string
          format: date-time
          description: Required when `status` is `snoozed`. The date must be in the future.
        severity:
          $ref: '#/components/schemas/VulnerabilitySeverity'
          description: New severity for every listed finding.
        severity_reason:
          type: string
          maxLength: 1000
          description: Optional reason for the severity change.
    BulkUpdateVulnerabilitiesResponse:
      type: object
      required:
        - total
        - succeeded
        - failed
        - results
      properties:
        total:
          type: integer
          description: Number of unique vulnerability ids in the request.
        succeeded:
          type: integer
          description: >-
            Number of vulnerabilities that were updated or already had the
            requested values.
        failed:
          type: integer
          description: Number of vulnerabilities that were not updated.
        results:
          type: array
          items:
            type: object
            required:
              - vulnerability_id
              - ok
            properties:
              vulnerability_id:
                type: string
              ok:
                type: boolean
              detail:
                type: string
                description: >-
                  Reason for a failure, or `Already up to date` when no column
                  changed.
    VulnerabilityStatus:
      type: string
      enum:
        - open
        - in_progress
        - snoozed
        - fixed
        - ignored
        - not_affected
    VulnerabilitySeverity:
      type: string
      enum:
        - critical
        - high
        - medium
        - low
    ErrorResponse:
      type: object
      properties:
        detail:
          type: string
          description: Human-readable explanation of the error.
        code:
          type: string
          description: >-
            Stable machine-readable error code. `insufficient_scope` means the
            token does not hold the scope that this endpoint requires.
        required_scope:
          $ref: '#/components/schemas/ApiV1Scope'
          description: >-
            Scope that the caller must add to the token. Returned with the
            `insufficient_scope` code.
        docs:
          type: string
          format: uri
          description: Documentation page that explains how to resolve the error.
        hint:
          type: string
          description: >-
            One instruction that resolves the error. For `insufficient_scope`, a
            CLI session gets the `strix cloud session scopes set full` or `strix
            cloud login --scope-profile full` command, and an API token gets the
            settings page where the user creates a token with the scope. When
            the owner's role cannot hold the scope, the hint asks for a role
            change instead.
      required:
        - detail
    ApiV1Scope:
      type: string
      enum:
        - scans:read
        - scans:write
        - vulnerabilities:read
        - vulnerabilities:write
        - dependencies:read
        - schedules:read
        - schedules:write
        - assets:read
        - assets:write
        - organizations:read
        - organizations:write
        - members:read
        - members:write
        - invitations:read
        - invitations:write
        - webhooks:read
        - webhooks:write
        - tokens:write
        - audit:read
        - pr_reviews:read
        - pr_reviews:write
        - connectors:read
        - connectors:write
        - knowledge:read
        - knowledge:write
        - uploads:write
        - integrations:read
        - integrations:write
        - chat:read
        - chat:write
        - scans:message
        - analytics:read
        - llm:read
        - llm:write
        - test_users:read
        - test_users:write
        - discovery:read
        - discovery:write
        - license:read
        - supply_chain:read
        - supply_chain:write
        - billing:read
        - billing:write
        - logs:read
  responses:
    BadRequest:
      description: Bad request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    Unauthorized:
      description: Missing or invalid API token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    Forbidden:
      description: >-
        Insufficient permissions or missing scope. A missing scope returns the
        `insufficient_scope` code, the `required_scope` field, and a `hint` with
        the command or page that grants the scope, so a client can request the
        correct scope and retry.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    InternalError:
      description: Internal server error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        API token obtained from the Tokens endpoint or CLI device login. Include
        as `Authorization: Bearer <token>`. Requests made with a managed CLI
        session also include `X-Strix-Workspace: <organization_id>` to pin a
        process to the workspace it started in; recovery endpoints report the
        current workspace after a concurrent switch.

````