CVE-2026-1668: Input Validation Vulnerability on Multiple Omada Switches
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.2% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 13, 2026
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 64th percentile
- CWE
- CWE-20
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · TPLink
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tp-link | omada sg2005p-pd firmware | cpe:2.3:o:tp-link:omada_sg2005p-pd_firmware |
| tp-link | omada sg2005p-pd | cpe:2.3:h:tp-link:omada_sg2005p-pd |
| tp-link | omada sg2008 firmware | cpe:2.3:o:tp-link:omada_sg2008_firmware |
| tp-link | omada sg2008 | cpe:2.3:h:tp-link:omada_sg2008 |
| tp-link | omada sg2008p firmware | cpe:2.3:o:tp-link:omada_sg2008p_firmware |
| tp-link | omada sg2008p | cpe:2.3:h:tp-link:omada_sg2008p |
| tp-link | omada sg2016p firmware | cpe:2.3:o:tp-link:omada_sg2016p_firmware |
| tp-link | omada sg2016p | cpe:2.3:h:tp-link:omada_sg2016p |
| tp-link | omada sg2210mp firmware | cpe:2.3:o:tp-link:omada_sg2210mp_firmware |
| tp-link | omada sg2210mp | cpe:2.3:h:tp-link:omada_sg2210mp |
| tp-link | omada sg2210p firmware | cpe:2.3:o:tp-link:omada_sg2210p_firmware |
| tp-link | omada sg2210p | cpe:2.3:h:tp-link:omada_sg2210p |
and 66 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link omada sg2005p-pd firmware1.0.0 and later · before 1.0.19
- tp-link omada sg2008 firmware4.20.0 and later · before 4.20.17
- tp-link omada sg2008 firmware4.30.0 and later · before 4.30.1
- tp-link omada sg2008p firmware3.20.0 and later · before 3.20.17
- tp-link omada sg2008p firmware3.30.0 and later · before 3.30.1
- tp-link omada sg2016p firmware1.20.0 and later · before 1.20.17
- tp-link omada sg2016p firmware1.30.0 and later · before 1.30.1
- tp-link omada sg2210mp firmware4.20.0 and later · before 4.20.18
- tp-link omada sg2210mp firmware5.0.0 and later · before 5.0.15
- tp-link omada sg2210mp firmware5.20.0 and later · before 5.20.1
- tp-link omada sg2210p firmware5.20.0 and later · before 5.20.18
- tp-link omada sg2210p firmware5.30.0 and later · before 5.30.1
- tp-link omada sg2210xmp-m2 firmware1.0.0 and later · before 1.0.19
- tp-link omada sg2218 firmware1.30.0 and later · before 1.30.1
- tp-link omada sg2218 firmware1.20.0 and later · before 1.20.17
- tp-link omada sg2218p firmware1.20.0 and later · before 1.20.17
- tp-link omada sg2218p firmware2.0.0 and later · before 2.0.14
- tp-link omada sg2218p firmware2.20.0 and later · before 2.20.2
- tp-link omada sg2428lp firmware1.0.0 and later · before 1.0.13
- tp-link omada sg2428p firmware5.20.0 and later · before 5.20.20
Versions reported by the vendor
Affected version ranges reported by the assigning authority (TPLink). Independent of NVD's CPE analysis and usually ahead of it.
TP-Link Systems Inc. SG2005P-PD 1.x
- before 1.0.19 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2008 4.2x
- before 4.20.17 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2008 4.3x
- before 4.30.1 Build 20260127 Rel.32017affected
TP-Link Systems Inc. SG2008P 3.2x
- before 3.20.17 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2008P 3.3x
- before 3.30.1 Build 20260127 Rel.32017affected
TP-Link Systems Inc. SG2016P 1.2x
- before 1.20.17 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2016P 1.3x
- before 1.30.1 Build 20260127 Rel.32017affected
TP-Link Systems Inc. SG2210MP 4.2x
- before 4.20.18 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2210MP 5.2x
- before 5.20.1 Build 20260127 Rel.32017affected
TP-Link Systems Inc. SG2210MP 5.x
- before 5.0.15 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2210P 5.2x
- before 5.20.18 Build 20260121 Rel.53429affected
TP-Link Systems Inc. SG2210P 5.3x
- before 5.30.1 Build 20260127 Rel.32017affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:4 | 2026-04-06 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-30 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+23 d
- TodayNov 9, 2026+241 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- tangrsfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS 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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.