# Vulnerability Disclosure Policy

Surge publishes a public search API over its indexed pages; the guide is at https://surge.app/agents/agent-access.

Source: https://surge.app/vulnerability-disclosure/
Source observed: 2026-11-05T16:19:58.153Z
Last checked: 2026-11-12T19:32:27.968+00:00
Indexed: 2026-11-05T16:46:39.813+00:00

---

# Vulnerability Disclosure Policy

**Last updated:** February 7, 2025

We ask security researchers to read and follow this policy before reporting a vulnerability. We value reports submitted under this policy, but we do **not** offer monetary rewards for vulnerability disclosures.

## Reporting

If you believe you have found a security vulnerability relating to our system, submit a report to the address specified in the **Contact:** field of our published [`security.txt`](https://surge.app/.well-known/security.txt) file.

Include:

- The website, IP address, or page where the vulnerability can be observed.
- A brief description of the vulnerability type, such as “XSS vulnerability.”
- Benign, non-destructive proof-of-concept reproduction steps. These help us triage accurately and reduce duplicate reports or malicious exploitation, including subdomain takeovers.

## What to expect

We will respond within **5 working days** and aim to triage the report within **10 working days**. We will also aim to keep you informed of progress.

We assess remediation priority using impact, severity, and exploit complexity. Reports may take time to triage or address. You may ask about status, but please do not do so more than once every **14 days**, allowing our teams to focus on remediation.

We will notify you when the vulnerability is remediated and may invite you to confirm that the solution adequately addresses it.

After resolution, you may request to disclose your report. Please coordinate any public release with us.

## Guidance

### You must not

- Break any applicable law or regulation.
- Access unnecessary, excessive, or significant amounts of data.
- Modify data in our systems or services.
- Use high-intensity, invasive, or destructive scanning tools.
- Attempt or report any denial of service, including overwhelming a service with high request volume.
- Disrupt our services or systems.
- Submit reports about non-exploitable vulnerabilities or gaps from general “best practice,” such as missing security headers.
- Submit reports about TLS configuration weaknesses, such as “weak” cipher suites or TLS 1.0 support.
- Communicate vulnerabilities or related details except through the means described in our published `security.txt`.
- Social-engineer, phish, or physically attack our staff or infrastructure.
- Demand financial compensation to disclose a vulnerability.

### You must

- Comply with data-protection rules and protect the privacy of data we hold. Do not share, redistribute, or fail to secure data retrieved from our systems or services.
- Securely delete all data retrieved during research as soon as it is no longer required or within **1 month of the vulnerability being resolved**, whichever occurs first, unless data-protection law requires another period.

## Legalities

This policy is designed to align with common vulnerability-disclosure practice. It does not authorize conduct that violates the law or could cause us or partner organizations to breach legal obligations.

We consider security research and disclosure conducted consistently with this policy to be “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and other applicable computer-use laws such as Cal. Penal Code 502(c). We waive potential DMCA claims against you for circumventing technological measures protecting applications within this program's scope.

We want researchers to coordinate disclosure through our program without fear of legal consequences for good-faith compliance. We cannot bind third parties, so this protection does not necessarily extend to them. If uncertain about a specific action, ask us before taking it.

If research conducted as part of this program violates certain restrictions in our site policies, the safe-harbor terms permit a limited exemption.

---

[Read this page’s summary](https://surge.app/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fsurge.app%2Fvulnerability-disclosure%2F&trace=t_96494d7d69f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Surge’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://surge.app/agents/agent/faq?q={question}&trace=t_96494d7d69f3`

[Tool guide and examples](https://surge.app/agents/agent-access) · [OpenAPI](https://surge.app/agents/api/public/v1/openapi.json) · [Page TLDR form](https://surge.app/agents/agent-tools/page-tldr?url=https%3A%2F%2Fsurge.app%2Fvulnerability-disclosure%2F). Opening a form does not execute a tool.