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

Offensive Security

Bug bounty on security.txt offsec.com

Accepting reports security.txt mentions bounty
Go to program Website
Top reward
Not published
Top severity paid
Not published
Assets in scope
4
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 by email
security at offsec dot com
Replies within 1 day
As the policy promises.

Rewards

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

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes provides incentives for researchers to inform us of possible vulnerabilities in our sites in exchange for cash rewards.
Response
Within 1 days Quick replies . You’ll usually get answered in a few hours unless we think you’re trolling.
Hall of fame
Yes Extreme Gratitude from the Offensive Security team and a mention in our “heroes” section! (soon)

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

Scope

4 assets you may test.

Domains 3

  • cdimage.kali.org
  • kali.org
  • offsec.com

Products and areas 1

  • our sites

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Offensive Security's policy.

While testing

  • Be courteous . You’re about to tell someone their security stinks. Be nice about it.
  • Be descriptive . The more details you provide, the easier the bug will be to reproduce.
  • Read guidelines and communicate with the organization if questions arise.
  • Maintain professional integrity and avoid burdening your target with your tests. They won’t like this.
  • Respect the systems you’re testing. They are probably production.

Not accepted

  • Apache version disclosure
  • critical directory indexing vulnerabilities

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 3 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.