CVE-2026-22213

Riot-os Riot buffer overflow

9.8 CRITICALPublic exploitEPSS 0.40%

Published12 Jan 2026

Description

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 provided via the -s command-line option without bounds checking. This allows an attacker to supply an excessively long device name and overflow a fixed-size stack buffer, leading to process crashes and memory corruption.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Riot-os Riot< 2025.10 · 2026.01

Remediation

Fixed in

Riot-os Riot≥ 2025.10

References

https://github.com/RIOT-OS/RIOTProduct
https://seclists.org/fulldisclosure/2026/Jan/15ExploitMailing ListThird Party Advisory
https://www.riot-os.org/Product
https://www.vulncheck.com/advisories/riot-os-stack-based-buffer-overflow-in-tapslip6-utilityThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-22213 being actively exploited?

CVE-2026-22213 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.40%.

How severe is CVE-2026-22213?

CVE-2026-22213 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.40% probability of exploitation.

Which products are affected by CVE-2026-22213?

Affected products include Riot-os Riot.

How do I fix CVE-2026-22213?

Upgrade affected software to a fixed version, for example Riot-os Riot 2025.10 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-22213 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.