Real findingsfrom bug bounties.
The agents that hunt your surface also hunt live bug-bounty programs. Every finding is validated before it appears here: numbered and severity-rated, with a CVSS score where one is recorded. Titles stay redacted until the program discloses. Only real findings, in writing.
Incorrect Authorization
Superhuman (formerly Grammarly)
- CVSS
- 9.0
- CWE
- 863
The title stays redacted until the program discloses. The class of bug, the program, the severity and the score are public from day one.
| Vendor | ID | Description | CVE | Type | Date |
|---|---|---|---|---|---|
| EXNESS | RHE-002 | Pending disclosure criticalWith program | — | Insufficient postMessage Origin Validation | Aug 26, 2026 |
| Vercel Sandbox | RHE-004 | Pending disclosure highWith program | — | Server-Side Request Forgery (SSRF) | Aug 26, 2026 |
| Superhuman (formerly Grammarly) | RHE-008 | Pending disclosure highCVSS 8.2Pending disclosure | — | Missing Authentication | Aug 28, 2026 |
| Superhuman (formerly Grammarly) | RHE-009 | Pending disclosure criticalCVSS 9.0Pending disclosure | — | Incorrect Authorization | Aug 28, 2026 |
| Web.com Bug Bounty | RHE-014 | Pending disclosure highWith program | — | Improper Authentication | Sep 16, 2026 |
| Web.com Bug Bounty | RHE-018 | Pending disclosure highCVSS 8.2With program | — | Broken Access Control (BAC) | Sep 18, 2026 |
| toom Baumarkt GmbH - Webshop | RHE-031 | Pending disclosure highPending disclosure | — | Access Control | Oct 15, 2026 |
| toom Baumarkt GmbH - Webshop | RHE-035 | Pending disclosure highPending disclosure | — | Business Logic Errors | Oct 17, 2026 |
- RHE-002criticalAug 26, 2026
EXNESS
Pending disclosure
Insufficient postMessage Origin Validation—With program
- RHE-004highAug 26, 2026
Vercel Sandbox
Pending disclosure
Server-Side Request Forgery (SSRF)—With program
- RHE-008highAug 28, 2026
Superhuman (formerly Grammarly)
Pending disclosure
CVSS 8.2Missing Authentication—Pending disclosure
- RHE-009criticalAug 28, 2026
Superhuman (formerly Grammarly)
Pending disclosure
CVSS 9.0Incorrect Authorization—Pending disclosure
- RHE-014highSep 16, 2026
Web.com Bug Bounty
Pending disclosure
Improper Authentication—With program
- RHE-018highSep 18, 2026
Web.com Bug Bounty
Pending disclosure
CVSS 8.2Broken Access Control (BAC)—With program
- RHE-031highOct 15, 2026
toom Baumarkt GmbH - Webshop
Pending disclosure
Access Control—Pending disclosure
- RHE-035highOct 17, 2026
toom Baumarkt GmbH - Webshop
Pending disclosure
Business Logic Errors—Pending disclosure
Programs are the vendors' own bug-bounty programs, not customers. A finding's title is redacted until the program discloses it; the type, severity and score stay visible so you can see what class of bug the pipeline finds.
How an advisory gets here
- 01
Found on a live bug-bounty program
The hunting pipeline runs against live bug-bounty programs every day. What it finds there is the same class of finding it would find on your surface.
- 02
Validated before it counts
Deterministic re-check plus adversarial review. If impact can't be demonstrated, the finding doesn't ship; the same gate your own report passes.
- 03
Disclosed, then published
The program is notified first. An accepted finding appears as a reserved row until the program discloses; then the full entry publishes. Only real findings, in writing.
- 04
Misses written down where they exist
Where an approach was tried and didn't hold, the advisory record says so next to the confirmed finding: what was attempted, and why it didn't carry. A record that never shows a miss was curated, and curated evidence is worth less.
Find out what your surface shows.
The free check is read-only and returns a short written report on what your domain exposes.