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
3 of 15,219 reports · 227 analysed so far
- #365968N/AYour page has 2 blocking CSS resources. This causes a delay in rendering your page.Node.js · Memory Corruption · 2018–8votes
- #1141623N/AUnexpected input validation of octal literals in nodejs v15.12.0 and below returns defined values for all undefined octal literals.Node.js · Memory Corruption · 2021–4votes
- #629879N/Aloader.js is not secureNode.js · Command and Code Injection · 2020–3votes
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.