CVE-2026-22902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceQuNetSwitch contains a command injection vulnerability that allows a local attacker with administrator privileges to execute arbitrary commands on the underlying system. The vulnerability exists in how QuNetSwitch processes certain inputs, enabling command injection through the application interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.0.5.0906CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify QuNetSwitch versionLocate and read the installed version of QuNetSwitch from the application interface, system logs, or package management system. Compare the version number against the affected range (versions <= 2.0.5.0906).Affected if The installed version is 2.0.5.0906 or lower.
-
Review administrator access controlsExamine QuNetSwitch user management settings and confirm that only authorized administrators have access to the application. Check for any unauthorized administrator accounts or sessions.Affected if Unrecognized or unauthorized administrator accounts exist, or administrator credentials may be compromised.
-
Audit application command-processing interfacesExamine QuNetSwitch configuration for input fields or interfaces that process system commands. Look for areas where user-supplied data might be passed to system calls without sanitization.Affected if Weak or absent input validation is found in command-processing areas of the application.
A system is affected if QuNetSwitch version is 2.0.5.0906 or lower and the application has administrator access that could be exploited for command injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate QuNetSwitch to version 2.0.5.0906 or later to remediate this vulnerability. Since exploitation requires administrator access, ensure administrator credentials are properly secured and monitor for unauthorized administrative access.
QuNetSwitch 2.0.5.0906 or later
- 1. Check current QuNetSwitch version via the web interface or CLI to confirm the installed version.
- 2. Back up all QuNetSwitch configurations and critical data before upgrading.
- 3. Download QuNetSwitch version 2.0.5.0906 or later from the official QNAP website.
- 4. Follow QNAP's standard upgrade procedure for QuNetSwitch (typically via the QuNetSwitch web interface or CLI upgrade command).
- 5. After upgrade, verify the new version is installed and confirm the system is operational.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data