# CVE-2026-82079: Potential Leakage of Nintendo Switch System Information Through a Proximity-Based Remote Attack

> A stack-based buffer overflow in Nintendo Switch local wireless networking allows remote attackers within range to execute arbitrary code via crafted traffic.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-ccj4-6gq7-582f

## What is CVE-2026-82079?

CVE-2026-82079 is a high-severity memory corruption vulnerability in Nintendo Switch, published on 10 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A stack-based buffer overflow vulnerability in the Nintendo Switch local wireless networking functionality may allow an attacker within wireless range to execute arbitrary code using return-oriented programming (ROP) through crafted network traffic.
This issue affects Nintendo Switch: before 23.0.0.

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

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


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

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

## Is CVE-2026-82079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82079 is a high-severity memory corruption vulnerability in Nintendo Switch, published on 10 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82079 in the wild and no public exploit code.

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

## Sources

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

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