- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 2 days
- As the policy promises.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 2 days
Please allow a reasonable time (1-2 business days) for a response after reporting.
- Safe harbor
-
Partial
We expect you to make a good faith effort to avoid privacy violations, destruction of data, or degradation to our service during your research.
- Hall of fame
-
Yes
Red Hat would like to thank the following individuals and organisations that have privately reported security issues that affected Red Hat branded websites or online services and agreed to be listed.
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 4
- cloud.redhat.com
- connect.redhat.com
- developers.redhat.com
- redhat.com
Products and areas 1
- any Red Hat branded website or online service
Rules
What the policy asks of you, and the bug types it won't reward, quoted from RedHat's policy. "We" in these lines means the program, not this site.
While testing
-
We expect you to make a good faith effort to avoid privacy violations, destruction of data, or degradation to our service during your research.
-
Please avoid using tools that are likely to automatically generate significant volumes of traffic or otherwise cause operational problems for our sites.
Not accepted
-
Directory Listings and FTP sites.
-
Version Numbers.
-
Secure Certificate Issues (mismatched host names, expired certificates, support for older protocols such as SSLv3)
-
Reports from automated tools or scanners without manual verification and analysis
-
Theoretical attacks without proof of exploitability
-
Brute force attacks (e.g. on passwords or tokens)
-
Attacks involving any user accounts not created by you
-
Attacks involving physical access to a user's device, or involving a device or network that is already compromised
-
Missing security headers that do not lead directly to a vulnerability
-
Clickjacking
-
Cookies missing secure or HttpOnly flags
-
Bugs that rely on an unlikely user interaction
-
Issues that are the result of a user deliberately performing an insecure action (like sharing their password or API tokens publicly)
-
Social engineering of Red Hat staff or users
-
Issues related to password and account recovery processes
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.