> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/exploit-reproduction.md). # Exploit Reproduction Konvu stands your application up in an isolated sandbox and runs the exploit, so you get proof that a vulnerability is real instead of a severity score. Exploit Reproduction is the second of Konvu's two [triage](/konvu/triage-and-remediation/triage.md) methods. An [exploitability assessment](/konvu/triage-and-remediation/exploitability-assessment.md) tells you whether the conditions for an exploit hold in your code. A reproduction tests the exploit itself. Konvu builds your application at the affected version, deploys it in an isolated sandbox, and has an agent run the exploit against it. If the exploit fires, you get the requests, responses, and side effects that prove it. Use reproduction when you need proof before acting: a bug bounty report you are about to pay out, a pentest finding a team disputes, or a scanner finding you want to escalate. ## What Konvu reproduces | Finding type | Reproduced | Notes | | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Vulnerability reports](/konvu/get-started/bring-in-findings/external-reports.md) (bug bounty, pentests, scanner exports, AI code security tools) | Yes | Automatically after triage, or on request. | | Code findings (SAST) | Early access | GitHub CodeQL findings only. See [Reproducing Scanner Findings](/konvu/triage-and-remediation/exploit-reproduction/reproducing-scanner-findings.md). | | Dependency findings (SCA) | Early access | Findings Konvu has already assessed as **Exploitable**. See [Reproducing Scanner Findings](/konvu/triage-and-remediation/exploit-reproduction/reproducing-scanner-findings.md). | | Container findings | No | | | Secrets | No | Secrets are assessed for validity, impact, and exposure instead. See [Secrets](/konvu/triage-and-remediation/finding-types/secrets.md). | ## When a reproduction runs * **Automatically, for vulnerability reports.** When automation is set to reproduce, each new report is triaged, checked for duplicates, and reproduced if it passes both. Konvu configures this per organization. Contact your Konvu team to change it. * **On request.** Select **Reproduce** on a report or on an eligible finding's **Reproduction** tab. A report that triage rejected (out of scope, invalid) cannot be reproduced until it is re-triaged. See [Re-running Reproductions](/konvu/triage-and-remediation/exploit-reproduction/re-running-reproductions.md). ## How reproduction affects the result Reproduction changes the assessment result only when the run proves or disproves the finding: * **A successful reproduction marks the finding Exploitable**, even when the static assessment said otherwise. The finding shows **Exploitable · Reproduced**. * **A reproduction that disproves the finding marks it False Positive.** An Exploitable or Inconclusive finding shows **False Positive · Not reproducible**. The evidence appears on the **Reproduction** tab under **Not reproducible**. * **A Hardening or Inconclusive reproduction result never downgrades a finding.** The assessment result stands. An Exploitable finding still shows **Exploitable**. * **For vulnerability reports**, the reproduction result becomes the report's status. A sandbox can fail to trigger a real vulnerability, for example when the exploit needs a managed service the sandbox cannot run. So Konvu treats an Inconclusive result as missing proof, not as a disproof. ## In this section * [**How Reproduction Works**](/konvu/triage-and-remediation/exploit-reproduction/how-reproduction-works.md): The pipeline, the sandbox, what Konvu needs from you, and what it does not do. * [**Reading a Reproduction**](/konvu/triage-and-remediation/exploit-reproduction/reading-a-reproduction.md): Reproduction results and every section of the result. * [**Re-running Reproductions**](/konvu/triage-and-remediation/exploit-reproduction/re-running-reproductions.md): Run again, check whether a fix landed, and steer a wrong result. * [**Reproducing Scanner Findings**](/konvu/triage-and-remediation/exploit-reproduction/reproducing-scanner-findings.md): Eligibility and limits for SAST and SCA findings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.konvu.com/konvu/triage-and-remediation/exploit-reproduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.