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
WeaknessMemory Corruption
- Any class
- Cross-site Scripting1
- Server-Side Request Forgery1
- Command and Code Injection6
- Injection and Smuggling21
- File and Path Handling7
- Memory Corruption19
- Race Conditions4
- Denial of Service25
- Input Validation and Logic2
- Misconfiguration and Insecure Design2
- Cryptography19
- Information Disclosure3
- Authentication2
- Access Control33
- Other weaknesses4
- No weakness recorded5
19 of 15,219 reports · $250 in bounties · 227 analysed so far
- #3083428ValidCorrupted pointer in node::fs::ReadFileUtf8(const FunctionCallbackInfo<Value>& args) when args[0] is a string.Node.js · Memory Corruption · 2025 · Low–59votes
- #3736889InformativeNULL pointer dereference in node:sqlite DatabaseSync#applyChangeset() via malformed SQLite changesetNode.js · Memory Corruption · 2026 · High–44votes
- #3405778ValidTimeout-based race conditions make Uint8Array/Buffer.alloc non-zerofilledNode.js · Memory Corruption · 2026 · High–43votes
- #988103ValidNode.js: use-after-free in TLSWrapNode.js · Memory Corruption · 2021–27votes
- #3824331ValidNull Dereference in X509ToObjectNode.js · Memory Corruption · 2026 · Medium–22votes
- #1763817ValidTake over subdomain undici.nodejs.org.cdn.cloudflare.netNode.js · Memory Corruption · 2023–22votes
- #3833629ValidRe-entrant `nghttp2_session_mem_send()` during `nghttp2_session_mem_recv()` causes heap-use-after-free in Node.js HTTP/2Node.js · Memory Corruption · 2026 · High–17votes
- #3760016ValidNode.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (DoS)Node.js · Memory Corruption · 2026 · High–13votes
- #365968N/AYour page has 2 blocking CSS resources. This causes a delay in rendering your page.Node.js · Memory Corruption · 2018–8votes
- #784186Validnapi_get_value_string_X allow various kinds of memory corruptionNode.js · Memory Corruption · 2020$2507votes
- #335533ValidHTTP/2 Denial of Service VulnerabilityNode.js · Memory Corruption · 2020–6votes
- #1209681ValidOOB read in libuvNode.js · Memory Corruption · 2021–5votes
- #1178337ValidImproper handling of untypical characters in domain namesNode.js · Memory Corruption · 2021–4votes
- #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
- #965914Valid`fs.realpath.native` on darwin may cause buffer overflowNode.js · Memory Corruption · 2020–4votes
- #335608ValidDenial of Service: nghttp2 use of uninitialized pointerNode.js · Memory Corruption · 2020–4votes
- #335495ValidOut of order TLS handshake / application data messages lead to segmentation faultNode.js · Memory Corruption · 2020–3votes
- #340053InformativeUse After Free in crypto.randomFillNode.js · Memory Corruption · 2020–2votes
- #536954ValidVulnerability in http-parser & embedded NULL header handlingNode.js · Memory Corruption · 2020–1votes
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.