CVE-2026-22902 | QNAP QuNetSwitch 2.0.4.0415 os command injection (qsa-26-11)
VulDBArchived Mar 20, 2026✓ Full text saved
A vulnerability was found in QNAP QuNetSwitch 2.0.4.0415 . It has been declared as critical . The impacted element is an unknown function. Such manipulation leads to os command injection. This vulnerability is documented as CVE-2026-22902 . The attack needs to be performed locally. There is not any exploit available. It is recommended to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352107 · CVE-2026-22902 · QSA-26-11
QNAP QUNETSWITCH 2.0.4.0415 OS COMMAND INJECTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.4 $0-$5k 1.77+
Summaryinfo
A vulnerability was found in QNAP QuNetSwitch. It has been rated as critical. This affects an unknown function. Performing a manipulation results in os command injection. This vulnerability is reported as CVE-2026-22902. The attack requires a local approach. No exploit exists. Upgrading the affected component is advised.
Detailsinfo
A vulnerability classified as critical has been found in QNAP QuNetSwitch. This affects an unknown function. The manipulation with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A command injection vulnerability has been reported to affect QuNetSwitch. If a local attacker gains an administrator account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following version: QuNetSwitch 2.0.5.0906 and later
The weakness was disclosed by 產品安全漏洞獵捕計劃 as qsa-26-11. It is possible to read the advisory at qnap.com. This vulnerability is uniquely identified as CVE-2026-22902 since 01/13/2026. The exploitability is told to be easy. Attacking locally is a requirement. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.
Upgrading to version 2.0.5.0906 eliminates this vulnerability.
Productinfo
Vendor
QNAP
Name
QuNetSwitch
Version
2.0.4.0415
License
commercial
Website
Vendor: https://www.qnap.com/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Os command injection
CWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: QuNetSwitch 2.0.5.0906
Timelineinfo
01/13/2026 CVE reserved
03/20/2026 +66 days Advisory disclosed
03/20/2026 +0 days VulDB entry created
03/20/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: qnap.com
Advisory: qsa-26-11
Researcher: 產品安全漏洞獵捕計劃
Status: Confirmed
CVE: CVE-2026-22902 (🔒)
GCVE (CVE): GCVE-0-2026-22902
GCVE (VulDB): GCVE-100-352107
Entryinfo
Created: 03/20/2026 17:59
Changes: 03/20/2026 17:59 (69)
Complete: 🔍
Cache ID: 99:158:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸