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

Logo.dev

Vulnerability disclosure program on security.txt logo.dev

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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]
Partial safe harbor
Some legal protection; read the terms.
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 We don't run a paid bug bounty program.
Safe harbor
Partial We take no legal action against research that follows the rules below.

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

Scope

1 asset you may test, 4 excluded.

Domains 1

  • logo.dev
Out of scope (4)
  • Missing best-practice headers or DNS records with no exploit.
  • Publishable API keys ( pk_ ) visible in a website's source.
  • Reports from automated scanners with no demonstrated impact.
  • Vulnerabilities in third-party services we use; report those to the vendor.

Rules

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

While testing

  • Test only with accounts and API keys you own. Don't access, change or delete other people's data.
  • Don't degrade the service: no denial-of-service tests, load tests or automated scans that send high volumes of traffic.
  • No social engineering, phishing or physical attacks.
  • Give us reasonable time to fix an issue before you disclose it publicly.

Not accepted

  • Publishable API keys ( pk_ ) visible in a website's source.
  • Reports from automated scanners with no demonstrated impact.
  • Missing best-practice headers or DNS records with no exploit.
  • Vulnerabilities in third-party services we use; report those to the vendor.

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 12 Nov 2026. Last checked 2 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.