Tor Browser

Skip to content What this pays sorona.xyz pays 1.25× the program's reward, up to +$1,000 per finding, plus a complexity bonus of up to $1,000 for especially complex or well-chained bugs. Finding │ Program pays │ Through sorona.xyz Critical (Tor Browser asset row) │ $3,000 │ $3,750 High │ $2,000 │ $2,500 Medium │ $1,000 │ $1,250 Low │ $100 │ $125 Submit a vulnerability CVE history 0 Last 12 months 5 Lifetime Info disclosure 40 % Access control 20 % Parsing/validation 15 % Denial of service 10 % Latest advisories Loading the feed Overview Tor Browser is the Gecko fork built for anonymity, and it is small by install count next to Chrome or Firefox, single-digit millions of daily users, but exceptionally high consequence per user. It is the deanonymisation-resistance layer for journalists, dissidents, researchers and investigators, and the reference implementation of fingerprinting resistance that both Mullvad Browser and Brave's Tor mode build from, so a proxy-bypass or fingerprinting defect here carries a physical-safety impact profile rather than a data-loss one. The Tor Project pays for it on HackerOne out of a pool funded by the Internet Bug Bounty, and the Tor Browser asset row runs $100 for a low through $3,000 for a critical. sorona.xyz adds 1.25× on top of whatever the Tor Project awards, up to $1,000 more, plus a complexity bonus of up to $1,000 for a well-chained finding. Response times ~3 days First response not published Triage ~10 days Bounty In scope The program pays for supported versions of two products only, the Tor daemon and Tor Browser. This page is the Tor Browser asset row: the Gecko fork at gitlab.torproject.org/tpo/applications/tor-browser, graded up to critical, on the latest stable, alpha and nightly builds Tor Browser on desktop across Windows, macOS and Linux, and Tor Browser for Android, all carried by that one asset row The browser as shipped, meaning the whole Gecko engine as Tor patches it: the content process and its sandbox, SpiderMonkey, the networking stack, the extension surface and the add-ons the bundle ships The Tor Browser patch set itself: first-party isolation, the fingerprinting-resistance work, the security-level slider and the invariant that no traffic reaches the network outside the SOCKS proxy Bootstrapping and connection assist: the Tor Launcher path, bridge configuration and the pluggable transports the bundle integrates, obfs4 and Snowflake among them The updater and the signature checking behind it, which is the path an attacker would take to ship a build a user already trusts Out of scope The tor daemon itself, which the same program pays on its own asset row at up to $4,000 critical and which this row does not cover The Tor Project's hosted services, meaning torproject.org, the bug tracker and the server infrastructure, which the policy rules out by name Orbot, OONI and Tor Messenger, the other Tor Project products the scope list marks ineligible Unsupported and end-of-life builds. Supported means the latest stable, alpha and nightly, so a bug that only reproduces on an older release earns nothing Defects that reproduce unchanged in stock Firefox, which are Mozilla's code and get filed against Mozilla; the Tor Browser CVE record is small for that reason Model-generated findings submitted without manual verification and a working proof of concept, and the program also wants you to name the model you used Reports sent by email rather than through HackerOne, which the policy treats as forfeiting the bounty Most-valued findings A proxy bypass that puts traffic on the network outside the SOCKS proxy. It defeats anonymity outright and is the shape a critical takes here A deanonymisation primitive built on fingerprinting: any signal that tells one Tor Browser user apart from the rest of the population, since the defence only holds while everyone looks identical First-party-isolation breaks that let a site correlate a user across two other sites. Info disclosure is 40% of this asset's recorded distribution, the largest class on it Access-control failures in the Gecko patch set that reach a resource the anonymity model is supposed to keep partitioned, 20% of the record Bridge and pluggable-transport flaws that reveal a user is connecting through Tor at all, which in some jurisdictions is the entire risk Program rules Submit through sorona.xyz first. We validate, coordinate with the program's security team, and add the payout uplift on top of whatever it awards. Test only supported versions: the latest stable, alpha and nightly builds, all of which the scope row links directly AI-assisted findings need manual verification and a working proof of concept, and you must disclose which model you used Say which of the two paid assets you hit: Tor Browser and the Tor daemon are priced on separate rows, and the daemon pays more at critical File through HackerOne rather than email, which is the channel the program treats as the bounty-eligible one Rewards are funded by the Internet Bug Bounty, whose own intake has been paused since 27 March 2026; Tor's program is still open and paid $1,800 in the last 90 days, but confirm the pool before committing heavy effort Program stats 68 Reports resolved $20.5k Bounties paid 51% Response efficiency Disclosure Coordinated through The Tor Project on HackerOne, and unusually open about it: nothing in the policy restricts third-party involvement or requires written consent before you talk about a fixed bug. The program goes further and states that policy-compliant research is authorized conduct it will vouch for if someone else comes after you, so sorona.xyz can carry the report end to end and publication timing stays a conversation between you and Tor. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability