Security readout for executives and security teams
Plain-English summary
A local logged-in user could crash TinyOS's mcp2200gpio utility by abusing how it builds device paths from /dev/usb/ filenames. The known impact is availability loss for that utility, not confirmed data theft or remote compromise.
Executive priority
Treat as a moderate local availability risk. Prioritize environments where TinyOS tooling runs on shared systems, lab hosts, or operational workstations with multiple local users.
Technical view
TinyOS up to and including 2.1.2 is reported vulnerable to a stack-based buffer overflow in mcp2200gpio. Unsafe strcpy() and strcat() use during automatic device discovery can corrupt stack memory when processing crafted /dev/usb/ filenames. CVSS v4.0 score is 4.8 with local, low-complexity, low-privilege attack conditions.
Likely exposure
Exposure is likely limited to systems that install TinyOS and use or ship the mcp2200gpio utility. The source bundle does not identify affected downstream packages, distributions, or default installation paths.
Exploitation context
The CVE is not listed as KEV, and the bundle provides no evidence of active exploitation. A Full Disclosure reference is tagged as exploit material, so public technical details may exist, but exploitation requires local access and filename control under /dev/usb/.
Researcher notes
Evidence supports CWE-121 in mcp2200gpio path construction using strcpy()/strcat(). The bundle does not provide a named patched version, vendor advisory, or proof of code execution beyond stack corruption and crashes.
Mitigation direction
- Check TinyOS vendor guidance and repository updates for an official fix.
- Restrict use of mcp2200gpio on shared or untrusted multi-user systems.
- Limit local accounts that can influence device nodes or filenames under /dev/usb/.
- Monitor for unexpected mcp2200gpio crashes until remediation is confirmed.
Validation and detection
- Inventory systems running TinyOS up to and including 2.1.2.
- Confirm whether the mcp2200gpio utility is installed or used operationally.
- Review local permissions and workflows around /dev/usb/ device discovery.
- Check crash logs for mcp2200gpio failures consistent with memory corruption.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22212 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://seclists.org/fulldisclosure/2026/Jan/14CVE reference, VulnCheck · technical-description, exploit
- https://github.com/tinyos/tinyos-mainCVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/tinyos-stack-based-buffer-overflow-in-mcp2200gpioCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.