Intel · bug bounty
Disclosed bug bounty reports
Every publicly disclosed report on HackerOne the Atlas holds: HackerOne's own outcome, severity, the weakness as filed and the access the title states, and, for analysed reports, how the bug was found in our words.
SortMost upvoted
StatusAny
WeaknessDenial of Service
- Any class
- Cross-site Scripting4
- Open Redirect2
- Command and Code Injection11
- Injection and Smuggling5
- Deserialization and Object Injection1
- File and Path Handling2
- Memory Corruption11
- Denial of Service6
- Input Validation and Logic1
- Misconfiguration and Insecure Design1
- Cryptography3
- Information Disclosure4
- Authentication3
- Access Control3
- No weakness recorded16
6 of 15,219 reports · 161 analysed so far
- #2666849ValidUncontrolled Resource Consumption when parsing maliciously crafted XML with REXMLRuby · Denial of Service · 2025 · Medium–21votes
- #661722ValidWEBrick::HTTPAuth::DigestAuth authentication is vulnerable to regular expression denial of service (ReDoS)Ruby · Denial of Service · 2019–17votes
- #2271054InformativeDoS in bigdecimal's sqrt function due to miscalculation of loop iterationsRuby · Denial of Service · 2023–14votes
- #1165748Informative'net/ftp': Uncontrolled Resource Consumption (Memory/CPU)Ruby · Denial of Service · 2021–8votes
- #898614InformativeDRb denial of service vulnerabilityRuby · Denial of Service · 2021–1votes
- #363934InformativeSEGV in parse_rat()Ruby · Denial of Service · 2018–0votes
The status is HackerOne's own outcome. “Access (title)” is what the report's title states; “Access (analysis)” and techniques come from CyberSIXT's own analysis, a model's summary of the public report that may be wrong. Data as of 2026-11-14.