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

Pension Benefit Guaranty Corporation

Vulnerability disclosure program on Self-hosted pbgc.gov

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
5
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 PBGC does not provide payment to reporters for submitting vulnerabilities.
Response
Within 3 days If you share contact information, we will acknowledge receipt of your report within 3 business days.
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 PBGC 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

5 assets you may test, 2 excluded.

Domains 4

  • efiling.pbgc.gov
  • mypaa.pbgc.gov
  • pbgc.gov
  • securefoia.pbgc.gov

Web 1

  • pbgc.gov/mypba
Out of scope (2)
  • Any service not expressly listed above, such as any connected services
  • systems from our vendors

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Pension Benefit Guaranty Corporation'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.
  • 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 us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.
  • Engage in physical testing of facilities or resources
  • Send unsolicited electronic mail to PBGC users, including phishing messages
  • Execute or attempt to execute Denial of Service (DoS), Distributed Denial of Service (DDoS), Resource Exhaustion attacks, or other tests that impair access to or damage a PBGC system or data
  • Introduce malicious software

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 6 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.