Skip to content

Nitro bug bounty programs

nitro.build Updated

Nitro runs one public program: a Sorona bug bounty paying up to $6,000.

Top reward
$6,000
Sorona
Programs
1
1 pays cash
Targets in scope
11
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program Nitro runs.

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

11 targets. 7 excluded.

  • https://nitro.build

    Web

  • Caching: cached event handlers and cached functions, the keys they derive and the entries they write

    Products and areas

  • Public and server asset serving out of the compiled bundle

    Products and areas

  • Route rules in full, covering basicAuth, proxy, redirect, cache and header rules, and the order in which several of them compose on one request

    Products and areas

  • Server middleware and the global middleware chain, including how it applies to WebSocket upgrades and to request paths that do not look like ordinary routes

    Products and areas

  • The build and prerender pipeline that writes the compiled server bundle and rendered output into the workspace

    Products and areas

  • The h3 request pipeline Nitro is built on: routing, event handling, body parsing, header handling and response writing

    Products and areas

  • The hosting presets that compile that bundle for Node, Deno, Bun, Cloudflare Workers, Vercel, Netlify and AWS Lambda, where a preset's own request adaptation can diverge from the reference server

    Products and areas

  • The nitrojs/nitro repository itself, added to the program on 2026-01-28 and listed under Tier 1 (High Priority) as a source-code asset that is bounty-eligible up to critical severity. The asset is the repo, so Nitro's own server code is the target

    Products and areas

  • The proxy layer, proxyRequest and sendProxy included, along with the header, cookie and redirect handling they perform in both directions

    Products and areas

  • The storage layer and its drivers, where server state, cache entries and secrets are read and written

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 7

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Cloud-provider and deployment-specific issues, which belong to Vercel's main platform program rather than the open-source one

  • Denial of service that only reproduces at development time and has no production path

  • Examples, templates and documentation snippets rather than Nitro's own code

  • Overbroad route regex matching in the Vercel CDN preset reported without demonstrated impact

  • Reports without the mandatory working proof-of-concept zip, which are not eligible regardless of severity

  • Third-party dependency CVEs without a demonstrated end-to-end chain through Nitro itself

  • Weaknesses in an allowlist the developer configured themselves: the bypass has to be framework-owned

Recent changes

Reward and scope changes across every Nitro program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in Nitro products, from the NVD.

Search NVD
  • Nitro is a next generation server toolkit. Prior to 3.0.260429-beta, an attacker could turn a redirect route rule using wildcards rewrite into a cross-host redirect by sliding an extra slash in after the rule prefix. This vulnerability is fixed in 3.0.260429-beta.

  • Nitro is a next generation server toolkit. Prior to 3.0.260429-beta, an attacker could bypass a proxy route rule by sending percent-encoded path traversal (..%2f) in the URL, causing Nitro to forward a request that the upstream resolved outside the configured scope. This vulnerability is fixed in 3.0.260429-beta.

About this page

This page gathers every public program listed under nitro.build: 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.