← Opportunities

Security Bug Bounty Program — Mozilla

Funder
Mozilla · Security Bug Bounty Program ✅ Proven payer
Type / status
other · open
Amount
—
Deadline
rolling
“The Mozilla Security Bug Bounty Program is designed to encourage security research in Mozilla software and to reward those who help us make the internet a safer place.”
Ecosystems
Categories
security
Tech stack
Apply
https://www.mozilla.org/en-US/security/bug-bounty
Source
https://www.mozilla.org/en-US/security/bug-bounty
Fit
8% · poor fit · The Venture23 Aleo team works on ZK protocol engineering and cross-chain infrastructure, which is entirely outside Mozilla's scope of funding browser and application security vulnerabilities.
Trust
42% · model self-report 90% · first seen 2026-10-18 · v1
Verified
2026-11-14 · page still up, no closing language

Mozilla offers bounties for security vulnerabilities found in its software, including Firefox and other Mozilla applications, as well as its websites and services. Security researchers who discover original, unreported bugs in Mozilla's code can receive rewards based on the severity and impact of the vulnerability. Submissions must follow the program's eligibility rules and safe harbor guidelines, and reports should be filed through Mozilla's Bugzilla or reported to security@mozilla.org. Bounties can be donated to charity upon request.

Eligibility: Open to anyone who is not a Mozilla employee or contractor, not on a US sanctions list, not in a sanctioned country, old enough to receive payment in their jurisdiction, and who has not written the buggy code. Submissions must be original, unreported, and in Mozilla's code or incorporated third-party libraries/websites used by Mozilla.

Pipeline

Override status:

Funder track record · does Mozilla actually pay grants?

✅ Proven payer · 5 grantees found · last payout 2026-11-06 · ⚠ 1 complaint · checked 2026-11-17 · 0 forum reports, 6 web pages read, 20 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

Red flags

GranteeAmountDateEvidence
Saami Family—2026-11-06“The Saami Family is one of 20 inaugural grantees awarded funding and technical resources to build technologies for use in their field.” source
Albany Park Theater Projectup to $150,0002026-10-28“The 2026 cohort Albany Park Theater Project” source
PI Yuhao Kang (Geography and the Environment) and co-PIs Hanlin Li (School of Computing) and Ming Zhang (School of Architecture)—2026-10-27“PI Yuhao Kang (Geography and the Environment) and co-PIs Hanlin Li (School of Computing) and Ming Zhang (School of Architecture) received a Mozilla Foundation award for their project “Reimagining Cities Using Responsible” source
Godot Engine$50,0002019-04-17
page date
“Godot Engine revealed it has become the recipient of a $50,000 grant from the Mozilla Open Source Support Mission Partners program.” source
Tor$152,500undated“## Tor ($152,500)” source

Trust breakdown (2/3 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.190%model self-report

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.510%model rated 10%
ecosystem overlap0.250%none vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%none vs rust, leo, zk

Sources (1)

RoleDocumentFromFetched
primarySecurity Bug Bounty Program — MozillaWeb discovery: ecosystem sweep2026-10-18

History (1)

vChangedFields
12026-10-18created

Extracted text

## Introduction

The Mozilla Security Bug Bounty Program is designed to encourage security research in Mozilla software and to reward those who help us make the internet a safer place.

## General Eligibility

To be eligible for a reward under this program:

*   The security bug must be original and previously unreported. Duplicate submissions from external reporters within 48 hours will split the bounty between those reporters. If duplicate submissions are of unequal quality, the split will be at the level of the lesser report, and the higher-quality report will receive a pro-rated additional bounty on top of the split.
*   For issues in client applications, external submissions that have already been reported internally are not eligible for a bounty unless the internal bug is stalled and the external report enables us to fix the bug. We also reserve a seven-day period for internal automated methods to find the same bug—this could be due to the bug being a recent regression or new detection methods becoming available that have already been deployed internally. In general, we want to reward submissions for issues that we would not have been able to detect and /fix without that submission or where the additional external submission provides significant help in fixing a bug (e.g. by providing a reliable testcase while the internal issue doesn’t have one).
*   The security bug must be a part of Mozilla’s code, not the code of a third party. We will pay bounties for vulnerabilities in third-party libraries incorporated into shipped client code or third-party websites utilized by Mozilla.
*   You must not have written the buggy code or otherwise been involved in contributing the buggy code to the Mozilla project.
*   You must be old enough to be eligible to participate in and receive payment from this program in your jurisdiction, or otherwise qualify to receive payment, whether through consent from your parent or guardian or some other way.
*   You must not be an employee, contractor, or otherwise have a business relationship with Mozilla or any of its subsidiaries.
*   You should use your best effort not to access, modify, delete, or store user data or Mozilla’s data. Instead, use your own accounts or test accounts for security research purposes.
*   If you inadvertently access, modify, delete, or store user data, we ask that you notify Mozilla immediately at [security@mozilla.org](mailto:security@mozilla.org) and delete any stored data after notifying us.
*   You should also use your best effort not to harm the availability or stability of our services, for example, by running aggressive scanning of those services. Instead, use a local development instance of the service that you want to test.
*   Whenever it is explicitly stated in our program scope, you are expected to test on the provided instances (e.g. staging) instead of production.
*   You must not be on a US sanctions list or in a country (e.g. Cuba, Iran, North Korea, Crimea region of Ukraine, Sudan, and Syria) on the US sanctions list.
*   You must not exploit the security vulnerability for your own gain.
*   Before sharing any part of the security issue with a third party, you must give us a reasonable amount of time to address the security issue.
*   All submissions will be covered under [Mozilla's Website & Communications Terms of Use](/en-US/about/legal/terms/mozilla/), granting us permission to make use of all submissions.
*   All questions regarding the status of bug bounties should be directed to [security@mozilla.org](mailto:security@mozilla.org) and not added as comments on Bugzilla.
*   All submissions must also abide by [Bugzilla's Etiquette Policy](https://bugzilla.mozilla.org/page.cgi?id=etiquette.html). Bugzilla may automatically disable accounts if too many bugs are submitted that get marked Invalid; if this happens you can contact [security@mozilla.org](mailto:security@mozilla.org); however, please be aware that too many invalid submissions may cause any valid bugs reported to receive reduced payouts. Please ask us for suggestions of how to improve your submission quality.

Bounties can be donated to charity, please indicate this in the bug when filing or by contacting [security@mozilla.org](mailto:security@mozilla.org).

Do not threaten or attempt to extort Mozilla. We will not award a bounty if you threaten to withhold the security issue from us or if you threaten to release the vulnerability or any exposed data to the public.

## Safe Harbor

Mozilla strongly supports security research into our products and wants to encourage that research.

As a result, we will not threaten or bring any legal action against anyone who makes a good faith effort to comply with this Bug Bounty Program, or for any accidental or good faith violation of this policy. This includes any claim under the DMCA for circumventing technological measures to protect the services and applications eligible under this policy.

As long as you comply with this policy:

*   We consider your security research to be "authorized" under the Computer Fraud and Abuse Act,
*   We waive any restrictions in our applicable Terms of Service and [Acceptable Use Policy](/en-US/about/legal/acceptable-use/) that would prohibit your participation in this policy, for the limited purpose of your security research under this policy.

We understand that many Mozilla systems and services are interconnected with third-party systems and services. While we can authorize your research on Mozilla’s systems and services, and promise that Mozilla will not bring or threaten litigation against you for your efforts under this policy, we cannot authorize efforts on third-party products or guarantee they won’t pursue legal action against you. However, if a third party threatens or brings any legal action against you for your efforts under this policy, we are willing to make clear—to the Court, the public, or otherwise--that we authorized your efforts to test and research the security of Mozilla’s eligible systems and services.

**If you’re not sure whether your conduct complies with this policy, please contact us first at [security@mozilla.org](mailto:security@mozilla.org) and we will do our best to clarify.**

## Web and Client

Mozilla manages two different bug bounty programs. One focuses on Firefox and other Mozilla applications and the other covers our websites and services.

*   [Client Bug Bounty Guidelines](/en-US/security/client-bug-bounty/)
*   [Web Bug Bounty Guidelines](/en-US/security/web-bug-bounty/)