Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

SEC

By U.S. Securities and Exchange Commission Vulnerability disclosure program on Self-hosted sec.gov

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
4
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.

Response
Within 3 days We will do our best to acknowledge that your report has been received within 3 business days of receipt.
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, and we will work with you to understand and resolve the issue quickly. In addition, the SEC will not recommend or pursue legal action related to your research.
Hall of fame
Yes LORs are awarded exclusively for P1-P4 rated reports that have been validated, accepted, and confirmed as fixed.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

4 assets you may test, 3 excluded.

Domains 3

  • investor.gov No bounty
  • sec.gov
  • usa.gov No bounty

Products and areas 1

  • all internet-accessible systems or services
Out of scope (3)
  • Any connected services to commercial entities or other government agencies
  • systems from our vendors
  • Testing third-party applications, websites, or services that integrate with or link to or from SEC systems

Rules

What the policy asks of you, and the bug types it won't reward, quoted from SEC's policy.

While testing

  • Notify the SEC as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence.
  • Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide the SEC a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.
  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data such as resource exhaustion attacks
  • Physical testing of facilities or resources (e.g., office access, open doors, tailgating)
  • Social engineering (e.g., phishing, vishing) or sending unsolicited electronic mail to SEC users, including “phishing” messages
  • Introducing malicious software

Not accepted

  • Reports flagged as duplicates or identified as known issues do not qualify for an LOR.

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.