sorona.xyz bug bounty programs
node.js Updated
Sorona.xyz runs one public program: a Sorona bug bounty paying up to $1,500.
- Top reward
- $1,500
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 10
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program sorona.xyz runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Node.js
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | – | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
10 targets. 6 excluded.
-
https://github.com/nodejs/node
Web
-
Path, filename and URL handling across the fs and url APIs, especially the Windows-specific normalisation differences that let a check and a use disagree
Products and areas
-
The bundled dependencies as Node exposes them, wherever Node's own use of them is what creates the impact
Products and areas
-
The crypto and TLS bindings as Node drives them, including certificate and hostname verification and the defaults exposed to callers
Products and areas
-
The entire C and C++ layer: the native bindings, the stream and buffer implementations, and anything that turns a JavaScript-supplied length or offset into an out-of-bounds access
Products and areas
-
The module system end to end, covering CommonJS and ESM resolution, loaders and hooks, integrity enforcement, and anything that loads code the caller did not intend
Products and areas
-
The permission model in full, including its policy flags and every boundary it claims to enforce over files, network destinations and child processes
Products and areas
-
The process and isolation boundaries: child_process, worker_threads and vm, where argument or environment handling crosses from untrusted input into process creation
Products and areas
-
The project's SECURITY.md takes reports against Node.js core on any release line still in support. The whole runtime sits inside that: the JavaScript APIs, the native layer, and the bundled dependencies as Node itself uses them
Products and areas
-
The whole HTTP surface: HTTP/1.1 and HTTP/2 request handling, header, chunked-encoding and trailer parsing, and any divergence from a front-end proxy that enables request smuggling or desync
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 6
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Application-side misuse: passing user input to eval, child_process or a path API without validation and reporting the consequence
-
Defects that actually live in V8, which is Chromium's codebase and has its own pathway, or in libuv, unless you can show Node's own use of them is what creates the impact
-
One-line fixes for non-exploitable crashes, which the Patch Rewards rules will not reward, including crashes that come from resource exhaustion
-
Patches the maintainers decline, patches under one month or over twelve months old, and anything past three submissions a person a month
-
The npm CLI, which is a separately owned and separately paid asset even though it ships inside every Node install
-
Vulnerabilities in third-party npm packages rather than in Node.js core, which are an ecosystem problem with their own separate and currently paused programme
Recent changes
Reward and scope changes across every sorona.xyz program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under node.js: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.