Device crash via unbounded printfUART string expansion
Published Jan 14, 2026 · Updated Jan 14, 2026
Global buffer overflow in TinyOS 2.1.2 and earlier allows local users to crash devices via an oversized printfUART string. The custom formatter appends each %s argument with strcat into the 256-byte global debugbuf without checking its remaining capacity. Reachability requires local code to pass a caller-controlled string to printfUART; corruption can also alter adjacent global state or UART output.
Summary
What happened
Global buffer overflow in TinyOS 2.1.2 and earlier allows local users to crash devices via an oversized printfUART string. The custom formatter appends each %s argument with strcat into the 256-byte global debugbuf without checking its remaining capacity. Reachability requires local code to pass a caller-controlled string to printfUART; corruption can also alter adjacent global state or UART output.
The record
- CVE
- CVE-2026-22211
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- TinyOS
- Product
- TinyOS
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- TinyOS 2.1.2 printfUART global-buffer-overflow test harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo