CVE-2026-22900
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 use of hard-coded credentials vulnerability has been reported to affect QuNetSwitch. The remote attackers can then exploit the vulnerability to gain unauthorized access. 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 hard-coded credentials that allow remote attackers to gain unauthorized access to the system. The vulnerability is classified as a critical authentication bypass issue with a CVSS score of 9.8.
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.1.13077, < 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify QuNetSwitch is installedCheck system for QuNetSwitch application - look for the Qnap QuNetSwitch software package or service running on the deviceAffected if QuNetSwitch is present on the system
-
Determine installed QuNetSwitch versionAccess QuNetSwitch admin interface or check installed package version - typically found in software info, about page, or system logsAffected if Version falls between 2.0.1.13077 and 2.0.5.0905 (inclusive)
-
Confirm remote access is enabledCheck QuNetSwitch network settings or firewall configuration to determine if remote management/access interfaces are exposedAffected if Remote access or management interface is accessible from network
-
Review access logs for unauthorized attemptsExamine QuNetSwitch authentication and access logs for suspicious login activity, especially from unexpected IP addresses or at unusual timesAffected if Evidence of unauthorized access attempts or successful logins from unknown sources
User is affected if QuNetSwitch version is >= 2.0.1.13077 and < 2.0.5.0906 with remote access enabled, as hard-coded credentials could allow remote attackers to gain unauthorized access.
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 · scoped2.0.5.0906
Upgrade QuNetSwitch to version 2.0.5.0906 or later to replace hard-coded credentials with proper credential management. If immediate patching is not possible, restrict network access to the device and monitor for unauthorized access attempts.
QuNetSwitch 2.0.5.0906 or later
- 1. Check current QuNetSwitch version to confirm it is within the affected range (>= 2.0.1.13077 and < 2.0.5.0906)
- 2. Download QuNetSwitch version 2.0.5.0906 or later from the official QNAP website (www.qnap.com)
- 3. Follow QNAP's standard upgrade procedure for QuNetSwitch to apply the update
- 4. Verify the upgrade was successful by checking the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22900 — 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-22900 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