TinyUSB bug bounty programs
tinyusb.org Updated
TinyUSB 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
- 8
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program TinyUSB runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
TinyUSB
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
8 targets. 5 excluded.
-
https://docs.tinyusb.org/en/latest
Web
-
Endpoint buffer management, and the DCD and HCD portability layer between the stack and each silicon vendor's controller
Products and areas
-
Reports go in as GitHub Security Advisories on hathach/tinyusb, and upstream is the boundary: a vendor SDK copy or a downstream port counts only when the defect is in the upstream tree. Everything in that tree is in play
Products and areas
-
The class driver set as a whole: CDC-ACM, MSC and its SCSI command handling, HID, Audio, Video, DFU and the vendor class
Products and areas
-
The device stack in full: SETUP packet parsing and the dispatch of standard, class and vendor control requests
Products and areas
-
The DFU class specifically, a direct firmware-write primitive and the highest-consequence driver in the tree
Products and areas
-
The host stack in full, including configuration, interface, endpoint and HID report descriptor parsing, all of it read from a device the host has no reason to trust
Products and areas
-
The per-port glue for the boards and silicon families the tree supports, where a shared abstraction is implemented once per controller
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 5
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Crash-only one-liners, which Google explicitly declines to reward on the patch rail
-
For the Google money specifically, anything reported but never patched upstream, since that pathway pays only on a merge
-
Limitations of the OSS-Fuzz harness rather than the stack: the integration is x86_64 only and aarch64 is not yet supported, which is a tooling gap rather than a vulnerability
-
Patches over twelve months old, which Patch Rewards will not consider
-
Vendor SDK copies and downstream ports where the defect does not exist in upstream hathach/tinyusb
Recent changes
Reward and scope changes across every TinyUSB 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 tinyusb.org: 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.