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

Symfony

Vulnerability disclosure program on security.txt symfony.com

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
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]
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 appreciate that developers are trying to find security issues in Symfony and report them responsibly, but we are currently unable to pay bug bounties.

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

Scope

2 assets you may test, 2 excluded.

Domains 1

  • symfony.com

Source code 1

  • the code hosted on the main symfony/symfony Git repository
Out of scope (2)
  • classes provided to help for testing that should never be used in production (like for instance mock classes that contain Mock in their name or classes in the Test namespace)
  • debug tools that must never be enabled in production (including the web profiler or anything enabled when APP_DEBUG is set to true or APP_ENV set to anything but prod )

Rules

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

While testing

  • don't use the bug tracker and don't publish it publicly
  • While we are working on a patch, please do not reveal the issue publicly.

Not accepted

  • Any security issues found in debug tools that must never be enabled in production
  • Any security issues found in classes provided to help for testing that should never be used in production

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.