Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Node.js

Vulnerability disclosure program on Self-hosted nodejs.org

Accepting reports
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Replies within 5 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No The Node.js project no longer has a bug bounty program.
Response
Within 5 days Normally, your report will be acknowledged within 5 days, and you'll receive a more detailed response to your report within 10 days indicating the next steps in handling your submission.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test, 5 excluded.

Domains 1

  • nodejs.org

Source code 1

  • Node.js
Out of scope (5)
  • experimental platforms
  • node:vfs
  • QUIC and HTTP/3
  • third-party modules
  • V8 Sandbox

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Node.js's policy. "We" in these lines means the program, not this site.

While testing

  • Use isolated, controlled environments.
  • Do not test on production systems without prior authorization.
  • Do not attempt to access or modify other users' data.
  • Immediately stop testing if unauthorized access is gained accidentally.
  • Include only the minimum proof of concept required to demonstrate the issue.
  • Remove any malicious payloads or components that could cause harm.
  • All security reports must comply with our Code of Conduct .

Not accepted

  • Defense-in-depth issues
  • Malicious Third-Party Modules (CWE-1357)
  • Same-process self-harm
  • Prototype Pollution Attacks (CWE-1321)
  • Uncontrolled Search Path Element (CWE-427)
  • Uncontrolled Resource Consumption (CWE-400) on outbound connections
  • Vulnerabilities affecting software downloaded by Corepack
  • Exposing Application-Level APIs to Untrusted Users (CWE-653)
  • Build System Attacks Requiring Control of the Build Environment (CWE-78, CWE-114, CWE-276)
  • Unhandled 'error' Events on EventEmitters (CWE-248)
  • Exceptions Thrown by Application Callbacks (CWE-248)
  • CRLF Injection in writeEarlyHints()
  • Unauthorized or untrusted HTTP proxy deployments
  • Malicious protocol peers

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 6 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.