# CVE-2026-22212: TinyOS <= 2.1.2 Stack-Based Buffer Overflow in mcp2200gpio

> A local attacker can cause application crashes via stack memory corruption in TinyOS by exploiting unsafe string functions during device discovery.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-x7h6-xxfr-j6pv

## What is CVE-2026-22212?

CVE-2026-22212 is a medium-severity memory corruption vulnerability in TinyOS, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TinyOS versions up to and including 2.1.2 contain a stack-based buffer overflow vulnerability in the mcp2200gpio utility. The vulnerability is caused by unsafe use of strcpy() and strcat() functions when constructing device paths during automatic device discovery. A local attacker can exploit this by creating specially crafted filenames under /dev/usb/, leading to stack memory corruption and application crashes.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-22212?


## How do I fix CVE-2026-22212?

No fix has been published for CVE-2026-22212 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22212 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22212 and fix it if it is affected.

What it is: CVE-2026-22212 is a medium-severity memory corruption vulnerability in TinyOS, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22212 exists.

Affected product: TinyOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22212/ (Markdown: https://insights.sbomify.com/CVE-2026-22212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22212
- OSV: https://osv.dev/vulnerability/CVE-2026-22212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22212/
Summaries are generated and may contain mistakes; the official description above is the record.