Skip to content

RIOT OS bug bounty programs

riot-os.org Updated

RIOT OS 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
13
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program RIOT OS 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

13 targets. 6 excluded.

  • https://www.riot-os.org

    Web

  • CoAP handling in nanocoap and gcoap, including option parsing, block-wise transfer and the observe mechanism

    Products and areas

  • Filesystem support, storage drivers and the flash abstraction underneath them

    Products and areas

  • LoRaWAN and the IEEE 802.15.4 radio drivers, along with the link-layer code that parses frames straight off the air

    Products and areas

  • Peripheral and sensor drivers in the tree, which parse data from hardware an attacker may control

    Products and areas

  • SUIT firmware update handling: the CoAP trigger path, manifest parsing, signature verification and the flash write that follows

    Products and areas

  • The Bluetooth Low Energy integration and the other wireless transports in the tree

    Products and areas

  • The cryptographic modules and the PSA Crypto implementation, together with the DTLS and TLS integrations

    Products and areas

  • The DHCPv6 client and the other network configuration clients that act on unauthenticated responses from the network

    Products and areas

  • The GNRC network stack end to end, covering IPv6, 6LoWPAN fragmentation and reassembly, UDP, TCP and the neighbour-discovery layer

    Products and areas

  • The kernel: the scheduler, threading, inter-process communication, mutexes and the memory allocators

    Products and areas

  • The policy asks for any security issue by private mail to the project security address, publishes a GPG key for it and sets out declassification rules. It draws no boundary narrower than the RIOT tree itself

    Products and areas

  • The USB device stack and the shell reachable over serial, which a great many deployments leave enabled

    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 code written against RIOT that misuses an API in a way the documentation warns against

  • Board configurations that deliberately leave a debug shell or an unauthenticated service enabled

  • Denial of service that amounts to jamming the radio or flooding the link

  • Downstream products and vendor forks built on RIOT rather than the upstream tree

  • Physical attacks on a node an attacker already holds, including reading flash over a debug port

  • Third-party packages pulled in through the package system, unless RIOT's own use of them is what makes the defect reachable

Recent changes

Reward and scope changes across every RIOT OS 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 RIOT OS products, from the NVD.

Search NVD
  • RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. In 2026.01 and earlier, the default handler for the well_known_core resource coap_well_known_core_default_handler writes user-provided option data and other data into a fixed size buffer without validating the buffer is large enough to contain

  • RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. In version 2025.10 and prior, multiple out-of-bounds read allow any unauthenticated user, with ability to send or manipulate input packets, to read adjacent memory locations, or crash a vulnerable device running the 6LoWPAN stack. The received

  • RIOT OS versions up to and including 2026.01-devel-317 contain a stack-based buffer overflow vulnerability in the tapslip6 utility. The vulnerability is caused by unsafe string concatenation in the devopen() function, which constructs a device path using unbounded user-controlled input. The utility uses strcpy() and strcat() to concatenate the fixed prefix '/dev/' with a user-supplied device name

  • RIOT OS versions up to and including 2026.01-devel-317 contain a stack-based buffer overflow vulnerability in the ethos utility due to missing bounds checking when processing incoming serial frame data. The vulnerability occurs in the _handle_char() function, where incoming frame bytes are appended to a fixed-size stack buffer without verifying that the current write index remains within bounds. A

  • RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When copying the contents of the first fragment (offset=0) into the reassembly buffer, no size check is performed. It is possible to force t

  • RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When receiving an fragmented IPv6 packet with fragment offset 0 and an empty payload, the payload pointer is set to NULL. However, the imple

  • RIOT-OS, an operating system that supports Internet of Things devices, has an ineffective size check implemented with `assert()` can lead to buffer overflow in versions up to and including 2025.04. Assertions are usually compiled out in production builds. If assertions are the only defense against untrusted inputs, the software may be exposed to attacks that utilize the lack of proper input checks

  • RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A malicious actor can send a IEEE 802.15.4 packet with spoofed length byte and optionally spoofed FCS, which eventually results into an endless loop on a CC2538 as receiver. Before PR #20998, the receiver would check for the location of the CRC

About this page

This page gathers every public program listed under riot-os.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.