HackerOne · disclosed reports
Information Disclosure
43 disclosed reports · $22,500 paid · 43 valid
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. A report opens its page here: our analysis where there is one, and the link to HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
Open HackerOne on HackerOne- reports
- 43
- valid
- 43
- paid a bounty
- 15
Every one of the 43 is a mark on the map. Named now: 1 to 26, most upvoted first.
- The /reports/:id.json endpoint discloses potentially sensitive user attributes when reporter summary is present
- Public GitHub repositories for multiple HackerOne managed triage team profiles contain private HackerOne reports information
- Google Docs link in JS files allows editing & reading survey information
- Unauthorized access to metadata of undisclosed reports that were retested
- Disclosure of `payment_transactions` for programs via GraphQL query
- 404-response contains debug-information with all headers
- Total Paid Bounty Paid can be disclose
- Team object in GraphQL disclosed private_comment
- Unauthorized user can obtain `report_sources` attribute through Team GraphQL object
- Private program disclosure via `vpn_suspended` GraphQL query
- GraphQL field on Team node can be used to determine if External Program runs invite-only program
- New Hacktivity features:Bounty rewards leakage Where programs doesn’t decide to disclose bounty in limited disclosure report
- Team object in GraphQL disclosed total number of whitelisted hackers
- "Bounties paid in the last 90 days" discloses the undisclosed bounty amount in program statistics
- HackerOne Undisclosed Report Leak via PoC of Full Disclosure on Hacktivity
- A HackerOne employee's GitHub personal access token exposed in Travis CI build logs
- Attachment object in GraphQL continues to grant access to files, even if they are removed from rendering
- Partial report contents leakage - via HTTP/2 concurrent stream handling
- Program metrics disclosed response_efficiency_percentage via /program_name json response despite the team decided not to show on their profile
- HackerOne customer submitted sensitive link to VirusTotal, exposing confidential information
- Team object exposes amount of participants in a private program to non-invited users
- HackerOne Staging uses Production data for testing
- Total bounties paid amount is disclosed because of redesign of the Program Profiles
- Attachment in published HackerOne report exposure private program
- information disclosure of another company bug on video.
- Disclosure of the name of a program that has a private part with an external link
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.