Environmental Protection Agency
By United States Environmental Protection Agency Vulnerability disclosure program on Self-hosted epa.gov
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
By submitting a vulnerability, the researcher acknowledges that, there is no expectation of payment for these services and waives any future payment claims against the U.S. Government related to the submission.
- Response
-
Within 3 days
Within (3) business days, we will acknowledge that your report has been received.
- Safe harbor
-
Full
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and EPA will not recommend or pursue legal action related to your research.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 3 excluded.
Domains 1
- epa.gov
Products and areas 1
- all EPA-managed systems and services that are accessible from the Internet
Out of scope (3)
- any connected services
- non-federal systems from our vendors
- third-party applications, websites, or services that integrate with or link to or from EPA systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Environmental Protection Agency's policy. "We" in these lines means the program, not this site.
While testing
-
Notify us as soon as possible after you discover a real or potential security issue.
-
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Do not submit a high volume of low-quality reports.
-
Only use exploits to the extent necessary to confirm a vulnerability’s presence.
-
Engage in physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing;
-
Execute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks or introduce malicious software;
-
Use an exploit to exfiltrate data, establish command line access, establish a persistent presence on EPA systems, or “pivot” to other EPA systems.
-
Cease testing and notify us immediately upon discovery of a vulnerability,
-
Purge any stored EPA nonpublic data upon reporting a vulnerability.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.