# CVE-2026-102693: RIOT: Remote Stack Buffer Overflow in ATWINC15x0 driver via unsanitized SSID

> A stack buffer overflow in the ATWINC15x0 driver allows remote attackers to execute code or cause denial of service via a malicious SSID.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-gwgv-6976-hxrg

## What is CVE-2026-102693?

CVE-2026-102693 is a critical memory corruption vulnerability in RIOT-OS RIOT, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RIOT is an open-source microcontroller operating system designed for Internet of Things devices and other embedded systems. Prior to 2026.04, the ATWINC15x0 driver's _atwinc15x0_sta_set_current_ssid function uses strcpy to copy an SSID without checking the destination size. When MODULE_ATWINC15X0_DYNAMIC_CONNECT is enabled, a nearby attacker can advertise a malformed or oversized SSID that is processed during Wi-Fi scanning, causing memory corruption and potentially a hard fault, denial of service, or code execution. This issue is fixed in version 2026.04.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2026-102693 being exploited?

There is no known exploitation of CVE-2026-102693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102693 is a critical memory corruption vulnerability in RIOT-OS RIOT, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102693 in the wild and no public exploit code.

Affected product: RIOT-OS RIOT. 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-102693/ (Markdown: https://insights.sbomify.com/CVE-2026-102693/index.md)
```

## Sources

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

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