CVE-2026-1668
A public proof of concept exists; no exploitation attested.
- Published2026-03-13
- Fixed in5.20.1 · 5.0.15 · 4.20.18
- WeaknessCWE-20 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-03-1319:53CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-1668?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-1668?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.20 | ≥ 5.20.0, < 5.20.1 | 5.20.1 | NVD |
| 5.0 | ≥ 5.0.0, < 5.0.15 | 5.0.15 | NVD |
| 4.20 | ≥ 4.20.0, < 4.20.18 | 4.20.18 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.20 | ≥ 2.20.0, < 2.20.2 | 2.20.2 | NVD |
| 2.0 | ≥ 2.0.0, < 2.0.14 | 2.0.14 | NVD |
| 1.20 | ≥ 1.20.0, < 1.20.17 | 1.20.17 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.30 | ≥ 4.30.0, < 4.30.1 | 4.30.1 | NVD |
| 4.20 | ≥ 4.20.0, < 4.20.17 | 4.20.17 | NVD |
36 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Tp-link omada sg2210mp firmware to 5.20.1 · 5.0.15 · 4.20.18
Advisories and patches
- support.omadanetworks.comVendor Advisory
Detection
read 2026-10-23 19:24 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedtangrs/cve-2026-1668-pocwuyou6956-glitch/cve-2026-1668-poc PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionnone2026-03-13
- OpenCVESSVC decisionnone—
- CNACVSS 4.07.7read 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-20read 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-03-13
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-1668?
Is CVE-2026-1668 actively exploited?
What is the CVSS score for CVE-2026-1668?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.