Responsible Use Policy
Vulnerability information is dual-use. This policy sets out how we expect cve-explore.com data, the API, and the MCP server to be used.
Last updated: 2026-04-29
cve-explore.com exists to make publicly disclosed vulnerability information faster to find and easier to consume — for defenders, researchers, and AI agents working on their behalf. The same data can be misused. This page sets out how we expect it to be used, and what we will do when it is not.
1. Core principles
- Defence over offence. Use what you find here to patch, detect, and harden — not to attack.
- Authorised testing only. Run proof-of-concept code only against systems you own or have explicit written permission to test.
- No real-world targeting from AI agents. Agents using our MCP server must not chain CVE data into automated exploitation of third-party systems.
- Don't cause harm. Even authorised testing must avoid collateral damage to data, users, or third parties.
2. Authorisation comes first
Vulnerability records on this site frequently link to public proof-of-concept exploits hosted by third parties. Linking is not an invitation to use. Before running any PoC against a system:
- Confirm in writing that you are authorised to test the target. A scope-of-work, bug-bounty programme rules, or a signed penetration-testing agreement are typical authorisations.
- Use an isolated, instrumented environment whenever possible. Production-level testing should be a deliberate, scoped activity with rollback plans.
- Respect data minimisation — do not exfiltrate, retain, or redistribute personal data uncovered during testing.
3. AI-generated PoCs
Some PoCs on this site are generated by an AI model from the public CVE description. They carry an AI-GENERATED · UNVERIFIED badge and an explicit warning. Specifically:
- They have not been executed against a real target.
- They have passed a syntax check and a structured AI self-review, and nothing more.
- They are research leads, not verified exploits. Treat them as you would any unverified report.
- The locked safety copy alongside each AI PoC is part of the content and must remain in any quotation or republication.
4. Coordinated disclosure
If you discover a vulnerability that is not already public:
- Report it to the affected vendor first. Most vendors operate a security mailbox or a published
SECURITY.txt. - Allow a reasonable period (commonly 90 days) for a fix before public disclosure.
- Coordinate with a CNA — MITRE, vendor PSIRT, or a national CSIRT — for CVE assignment.
We are not a CNA. We index records that have already entered the public CVE corpus.
5. API and MCP abuse
Our public API and MCP server have rate limits to keep the service available to everyone. Behaviours we treat as abuse include:
- Rotating IP addresses or API keys to evade rate limits.
- Bulk scraping of the entire corpus for redistribution outside our published bulk-data channels.
- Using the MCP server to drive an automated exploitation pipeline against systems you do not own.
- Generating excessive load that materially degrades the service for other users.
We may revoke API keys, suspend accounts, or block IP ranges that engage in any of the above. We aim to warn before we block, but we reserve the right to act immediately when service stability or safety is at risk.
6. Compliance with law
You are responsible for complying with the laws of your jurisdiction. Unauthorised access, modification, or disruption of computer systems is criminal in most jurisdictions — including under the Computer Fraud and Abuse Act (US), the Computer Misuse Act (UK), the Convention on Cybercrime (Council of Europe), and their domestic equivalents. Possession or distribution of certain dual-use tools may also be regulated. Nothing on this site is an authorisation to breach any of these laws.
7. Reporting abuse
To report misuse of cve-explore.com, an account, or an API key, email abuse@cve-explore.com. To report a security flaw in the service itself, email security@cve-explore.com. Please give us reasonable time to respond before public disclosure.
Terms Privacy Responsible use Questions? legal@cve-explore.com