Is CVE-2026-22213 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-22213 being exploited in the wild.

How severe is CVE-2026-22213?

Critical severity, with a CVSS score of 9.8, published 12 January 2026.

Which products and versions are affected?

Riot-Os Riot up to and including 2026.01-devel-317.

Is there a fix for CVE-2026-22213?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-22213 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-22213?

Check whether you run Riot-Os Riot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-22213: RIOT OS stack-based buffer overflow in tapslip6 utility

CVE-2026-22213 · Severity: critical · CVSS 9.8 · Published 2026-01-12

RIOT OS is an open-source operating system designed for Internet of Things (IoT) devices. A security vulnerability exists in its tapslip6 utility, which is used to bridge network traffic between a computer and an IoT device. An attacker could exploit this flaw to crash the utility or potentially execute unauthorized code, which could disrupt development environments or compromise systems where the tool is run with elevated privileges.

Technologies: Riot-Os Riot. Vendors: Riot-Os.

Quick answers

Is CVE-2026-22213 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-22213 being exploited in the wild.
How severe is CVE-2026-22213?: Critical severity, with a CVSS score of 9.8, published 12 January 2026.
Which products and versions are affected?: Riot-Os Riot up to and including 2026.01-devel-317.
Is there a fix for CVE-2026-22213?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-22213 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-22213?: Check whether you run Riot-Os Riot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stack-based buffer overflow (CWE-121) exists in the tapslip6 utility of RIOT OS. The vulnerability is located in the devopen() function, which uses strcpy() and strcat() to construct a device path by concatenating the '/dev/' prefix with a user-supplied string from the -s command-line argument. Because the utility does not perform bounds checking on this input before copying it into a fixed-size 1024-byte stack buffer, a local attacker can provide an excessively long string to trigger the overflow. This can result in memory corruption, process crashes, or potential arbitrary code execution. While the attack requires local access to execute the utility, the tool is frequently run with root/administrative privileges during IoT development and testing.

Affected products

RIOT-OS RIOT OS up to and including 2026.01-devel-317

Timeline

2026-01-08: disclosed: Initial disclosure on Full Disclosure mailing list by Ron Edgerson
2026-01-12: advisory: NVD and VulnCheck published advisory details

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.