Zyte · Vulnerability Disclosure
Zyte Vulnerability Disclosure
Vulnerability disclosure
Zyte runs a coordinated vulnerability disclosure program on Hackerone.
CrawlingData ExtractionScrapingWeb ScrapingProxiesBrowser AutomationAnti-BanSERPAgent SkillsDeveloper Tools
Program: Hackerone
Disclosure Policy
Security Contact
Source
Vulnerability Disclosure
generated: '2026-08-29'
method: searched
source: https://www.zyte.com/terms-policies/responsible-disclosure-program/
provider: Zyte
providerId: zyte
program:
name: Responsible Disclosure Program (BugHunt)
url: https://www.zyte.com/terms-policies/responsible-disclosure-program/
http_status: 200
platform: self-hosted
third_party_platform: none
note: >-
Not on HackerOne, Bugcrowd or Intigriti — Zyte runs the program itself
through a form on the policy page. Notably it is NOT advertised via an RFC
9116 /.well-known/security.txt on any Zyte host (see
well-known/zyte-well-known.yml), so a machine looking for the program the
standard way will not find it.
rewards:
monetary: false
statement: >-
"At this time, Zyte does not offer financial rewards for the disclosure of
security vulnerabilities."
recognition: Security Researcher Hall of Fame, published on the same page with researcher consent.
response_commitments:
acknowledgement: within 24 hours
triage: up to 5 days
notification: Zyte notifies the reporter when the issue is fixed.
scope:
domains:
- zyte.com
- app.zyte.com
- storage.zyte.com
note: >-
api.zyte.com and docs.zyte.com are not named in the published in-scope list.
qualifying:
- Remote code execution (RCE)
- SQL/XXE injection and command injection
- Cross-site scripting (XSS)
- Server-side request forgery (SSRF)
- Misconfiguration issues on servers and application
- Authentication and authorization related issues
- Cross-site request forgery (CSRF)
non_qualifying:
- HTML injection and self-XSS
- Host header and banner grabbing issues
- Automated tool scan reports (web, SSL/TLS, Nmap)
- Missing HTTP security headers and cookie flags on insensitive cookies
- Rate limiting, brute force attack
- Login/logout CSRF
- Unrestricted file upload
- Open redirections
- Formula/CSV injection
- Vulnerabilities requiring physical access to the victim machine
- User enumeration (email, user ID)
- Phishing / spam, including SPF/DKIM/DMARC issues
- Vulnerabilities found in third-party services
- EXIF data not stripped on images
researcher_obligations:
- Only interact with accounts you own or have explicit permission to test.
- Perform research only within the published scope.
- Do not publish vulnerability details publicly.
- Keep information confidential until the issue is resolved.
report_contents_required:
- Vulnerability overview — description and potential impact
- Reproduction steps and proof of concept, video POC where available
- Researcher recognition details (name/handle and link) if Hall of Fame inclusion is wanted
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/zyte-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.