Banner object (1)

Hack and Take the Cash !

846 bounties in database
  Back Link to program      
Node.js logo
Hall of Fame


500 $ 


Reporting a Bug in Node.js

All security bugs in Node.js are taken seriously. Please report any security issues here.

Your report will be acknowledged within 24 hours, and you’ll receive a more detailed response within 48 hours indicating the next steps in handling your report.

After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue. These updates will be sent at least every five days, in practice, this is more likely to be every 24-48 hours.

Reporting a Bug in a third party module

Security bugs in third party modules should be reported to their respective maintainers and should also be coordinated via @nodejs-ecosystem.

Details regarding this process can be found in the Security Working Group repository __.

Disclosure Policy

Here is the security disclosure policy for Node.js

  • The security report is received and is assigned a primary handler. This person will coordinate the fix and release process. The problem is confirmed and a list of all affected versions is determined. Code is audited to find any potential similar problems. Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement.

  • A suggested embargo date for this vulnerability is chosen and a CVE (Common Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability.

  • On the embargo date, the Node.js security mailing list is sent a copy of the announcement. The changes are pushed to the public repository and new builds are deployed to Within 6 hours of the mailing list being notified, a copy of the advisory will be published on the Node.js blog.

  • Typically the embargo date will be set 72 hours from the time the CVE is issued. However, this may vary depending on the severity of the bug or difficulty in applying a fix.

  • This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however, it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.

Receiving Security Updates

Security notifications will be distributed via the following methods.

Comments on this Policy

If you have suggestions on how this process could be improved, please submit a pull request __or file an issue __.

Thank you for improving the security of Node.js and its ecosystem. Your efforts and responsible disclosure are greatly appreciated and will be acknowledged.

Internet Bug Bounty Qualification

Only critical vulnerabilities that demonstrate complete compromise of the system's integrity or confidentiality are eligible for a bounty - typically Arbitrary Code Execution or equivalent impact. While we encourage you to submit all potential issues, lower severity issues are not in scope at this time.

Impact | Amount
High Demonstrate that remote exploitation of this bug can be easily, actively, and reliably achieved. | $1,500+
Medium Demonstrate that remote exploitation of this bug is very likely (e.g. good control a register). | $1,000
Minimum Demonstrate the presence of a security bug with probable remote exploitation potential. | $500

Only vulnerabilities in Node.js core will be considered for eligibility. Submissions related to and other project websites are explicitly NOT eligible.

The project maintainers have final decision on which issues constitute security vulnerabilities. The Panel __will respect their decision, and we ask that you do as well.

It's important to keep in mind that not all submissions will qualify for a bounty, and that the decision to award a bounty is entirely at the discretion of the Panel.

FireBounty © 2015-2019

Legal notices