# CVE-2026-1668: Input Validation Vulnerability on Multiple Omada Switches

> Unauthenticated attackers can trigger memory corruption via crafted requests to the web interface, potentially leading to remote code execution or denial of service.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-fmw5-jxp8-6hq3

## What is CVE-2026-1668?

CVE-2026-1668 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. SG2005P-PD 1.x, published on 13 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The web interface on multiple Omada switches does not adequately validate certain external inputs, which may lead to out-of-bound memory access when processing crafted requests.  Under specific conditions, this flaw may result in unintended command execution.<br>An unauthenticated attacker with network access to the affected interface may cause memory corruption, service instability, or information disclosure.  Successful exploitation may allow remote code execution or denial-of-service.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation)

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

It affects 39 products.


Products: Tp-Link Omada Sg2005p-Pd Firmware, Tp-Link Omada Sg2008 Firmware, Tp-Link Omada Sg2008p Firmware, Tp-Link Omada Sg2016p Firmware, Tp-Link Omada Sg2210mp Firmware, Tp-Link Omada Sg2210p Firmware, Tp-Link Omada Sg2210xmp-M2 Firmware, Tp-Link Omada Sg2218 Firmware, Tp-Link Omada Sg2218p Firmware, Tp-Link Omada Sg2428lp Firmware, Tp-Link Omada Sg2428p Firmware, Tp-Link Omada Sg2452lp Firmware, Tp-Link Omada Sg3210 Firmware, Tp-Link Omada Sg3210x-M2 Firmware, Tp-Link Omada Sg3210xhp-M2 Firmware, Tp-Link Omada Sg3218xp-M2 Firmware, Tp-Link Omada Sg3428 Firmware, Tp-Link Omada Sg3428mp Firmware, Tp-Link Omada Sg3428x-M2 Firmware, Tp-Link Omada Sg3428x Firmware and 19 more.

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

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

## Is CVE-2026-1668 being exploited?

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

Public exploit code:

- Proof-of-concept exploit for CVE-2026-1668. (github_poc): https://github.com/tangrs/cve-2026-1668-poc
- https://github.com/wuyou6956-glitch/cve-2026-1668-poc (github_poc): https://github.com/wuyou6956-glitch/cve-2026-1668-poc

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1668 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. SG2005P-PD 1.x, published on 13 Mar 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-1668 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. SG2005P-PD 1.x. 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-1668/ (Markdown: https://insights.sbomify.com/CVE-2026-1668/index.md)
```

## Sources

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

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