---
title: "Vulnerability Report"
method: POST
path: "/api/v2/issues/vulnerabilityReport"
tags: ["Issues"]
---

# Vulnerability Report

`POST /api/v2/issues/vulnerabilityReport`

## Request

- Base URL: `https://zeropath.com`
- URL: `https://zeropath.com/api/v2/issues/vulnerabilityReport`
- Auth: API key in header `X-ZeroPath-API-Token-Id` and API key in header `X-ZeroPath-API-Token-Secret`

Render one issue as a standalone Markdown vulnerability report: title with severity, Status (review status, remediation status, remediation notes such as the ZeroPath pull request), technical Description, Severity with separately rated Impact and Likelihood explanations derived from the CVSS assessment, Exploitation scenario with lettered preconditions, and the Proposed fix as per-file patches (or the upgrade to apply, for dependency findings). Sections with no recorded data say so rather than being omitted. Model-written text of detected-secret findings is always withheld. Write the returned `markdown` to a file named `fileName` when the user asks for a report file.

## Request body

- IssuesGetInput
  - `organizationId` string
  - `issueId` string, required

## Response `200`

The issue rendered as a Markdown vulnerability report

- IssueVulnerabilityReport
  - `issueId` string, required
  - `fileName` string, required
  - `markdown` string, required

---

[API](https://skmtc.dev/zeropath/apis/zeropath-api.md) - [All operations](https://skmtc.dev/zeropath/apis/zeropath-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zeropath/apis/zeropath-api/revisions/126e9c80ba0d?raw)