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

Range

Vulnerability disclosure program on Self-hosted range.co

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.
No public write-ups
Keep findings private.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No We aren’t able to offer bounty rewards at this time, but deeply appreciate your contributions.
Safe harbor
Full We will not take legal action against you if you play by the rules and act in good faith.
Hall of fame
Yes Bug Bounty Hall of Fame

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.

Domains 5

  • api.range.co
  • in.range.co
  • meet.range.co
  • range.co
  • rt.range.co

Rules

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

While testing

  • Don’t make the bug public before it has been fixed.
  • Don’t attempt to gain access to another user’s account or data. Use your own test accounts for cross-account testing.
  • Don’t perform any attack that could harm the reliability/integrity of our services or data. DDoS/spam attacks are not allowed.
  • Do not impact other users with your testing, this includes testing for vulnerabilities in accounts you do not own.
  • Don’t use scanners or automated tools to find vulnerabilities.
  • No non-technical attacks such as social engineering, phishing, or physical attacks against our employees, users, or infrastructure.

Not accepted

  • Self-XSS
  • Login/Logout CSRF
  • CSRF configuration issue without exploitable proof of concept
  • Missing security headers which do not directly lead to a vulnerability
  • Vulnerabilities in third party components, depending on severity and exploitability
  • Rate Limit on emails sent during sign-up, sign-in, and change email confirmations
  • Previous email login links not invalidated in the event multiple login links are requested
  • EXIF not stripped from uploads, unless discoverable outside of the workspace
  • Denial of Service (DOS) and rate limiting issues
  • Bugs requiring exceedingly unlikely user interaction
  • Social engineering attacks
  • Flaws affecting the users of out-of-date browsers and plugins
  • Enumeration or information disclosure of non-sensitive information
  • Enumeration of information within the context of a single workspace
  • Lack of input validation without exploitable proof of concept
  • Email bombing and flooding

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.