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

Lyft

Bug bounty on Self-hosted lyft.com

Accepting reports
Go to program Website
Top reward
Not published
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.

Pays cash
Amounts are not published; ask before you invest time.
Report as the policy says
The policy page explains how.
No safe harbor
No promise about legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

The policy page does not state reward amounts that we could read. Check it before you test.

Scope

0 assets you may test, 2 excluded.

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

Out of scope (2)
  • Third-party implementations integrating the Lyft SDK
  • Third-party websites used by Lyft app, websites or affiliates

Rules

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

While testing

  • Do not disclose your reported findings to others until we've had an opportunity to respond and address them.
  • We discourage the use of vulnerability testing tools or other tools that generate significant volumes of traffic; using these tools may disqualify you from qualifying for a reward.
  • While researching, you must refrain from: Denial of service
  • Please do not access, record, download, or store PII. Doing so will automatically make you ineligible for a bounty.

Not accepted

  • XSS requiring legacy browsers
  • Self-XSS
  • SSL/TLS best practices
  • Reflected file download
  • Software version disclosure
  • Path or hostname disclosure in error messages
  • Logout CSRF
  • Missing HTTP header which does not lead to a direct vulnerability
  • Missing cookie flags, unless the absence can be abused by a legitimate workflow
  • Clickjacking without demonstration of impact
  • Account enumeration through brute-force attacks
  • CSV command execution

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.