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

Ministry of Justice

Vulnerability disclosure program on Self-hosted

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
0
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 1 day
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 Unfortunately, due to the MOJ’s funding structure, it is not currently possible for us to offer a paid bug bounty programme.
Response
Within 1 days After submitting your vulnerability report , you will receive an acknowledgement reply usually within 24 working hours of your report being received.
Safe harbor
Full The MOJ affirms that it will not seek prosecution of any security researcher who reports any security vulnerability on an MOJ service or system, where the researcher has acted in good faith and in accordance with this disclosure policy.
Hall of fame
Yes Where a report qualifies, we will offer to include you on our thanks and acknowledgement page .

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

Scope

0 assets you may test.

Self-hosted does not list the scope of this program publicly. Check its policy.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Ministry of Justice's policy. "We" in these lines means the program, not this site.

While testing

  • access unnecessary amounts of data. For example, 2 or 3 records is enough to demonstrate most vulnerabilities, such as an enumeration or direct object reference vulnerability
  • use high-intensity invasive or destructive technical security scanning tools to find vulnerabilities
  • violate the privacy of MOJ users, staff, contractors, services or systems.
  • communicate any vulnerabilities or associated details using methods not described in this policy, or with anyone other than their assigned MOJ security contact
  • modify data in MOJ systems or services which does not belong to the researcher
  • disrupt MOJ services or systems
  • social engineer, ‘phish’ or physically attack MOJ staff or infrastructure
  • disclose any vulnerabilities in MOJ systems or services to 3rd parties or the public, prior to the MOJ confirming that those vulnerabilities have been mitigated or rectified
  • We ask you to delete securely any and all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first.

Not accepted

  • volumetric vulnerabilities are not in scope - meaning that simply overwhelming a service with a high volume of requests is not in scope
  • TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support, are not in scope

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.