CVE-2026-24717
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 path traversal vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains an administrator account, they can then exploit the vulnerability to read the contents of unexpected files or system data. We have already fixed the vulnerability in the following versions: QTS 5.2.9.3492 build 20260507 and later QuTS hero h5.2.9.3499 build 20260514 and later QuTS hero h5.3.4.3500 build 20260520 and later QuTS hero h6.0.0.3459 build 20260409 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 · high confidenceA path traversal vulnerability in QNAP operating systems allows an authenticated remote attacker with administrator privileges to read arbitrary files on the system by manipulating file path references. This could expose sensitive system configuration files, credentials, or other data beyond the intended accessible directories.
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>= 5.2.0.2737, < 5.2.9.3492>= h5.0.0, < h5.2.9.3499>= h5.3.0.3115, < h5.3.4.3500>= h6.0.0.3324, < h6.0.0.3459CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
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 the installed QNAP firmware versionAccess the QNAP admin console and navigate to Control Panel > System > Firm Update, or use the command 'getcfg system version' via SSH to retrieve the current QTS or QuTS hero build number and version.Affected if The installed version falls within any of these ranges: QTS 5.2.0.2737 to < 5.2.9.3492; QuTS hero h5.0.0 to < h5.2.9.3499; QuTS hero h5.3.0.3115 to < h5.3.4.3500; or QuTS hero h6.0.0.3324 to < h6.0.0.3459
-
Confirm the exact build numberIn the admin console, go to Control Panel > System > About > Firmware Build, or run 'getcfg system build_number' via SSH to get the precise build number.Affected if The build number matches any version listed in the affected ranges above (e.g., any build below 3492 for QTS 5.2.x, below 3499 for QuTS hero h5.2.x, etc.)
-
Determine if remote admin access is enabledCheck if the QNAP device has the admin web interface exposed externally via Control Panel > System > General Settings > Administration, or review firewall rules and port forwarding configurations.Affected if The administrator web interface is accessible from untrusted networks, allowing remote authenticated attackers to reach the vulnerable endpoint.
-
Identify administrator accountsReview user accounts in Control Panel > Privilege > Users, noting which accounts have Administrator privileges, as the vulnerability requires an authenticated attacker with admin-level access.Affected if There are active administrator accounts accessible to an attacker, particularly any default or weak credentials that could be compromised.
-
Audit file permission settingsCheck Control Panel > Privilege > Shared Folders to verify which directories are accessible to administrator-level users, as the path traversal could allow escaping the intended folder scope.Affected if Administrators have access to any file browsing or file management features, as the vulnerability exploits path traversal in these functions.
The device is affected if it runs QTS or QuTS hero with a version or build number within any of the specified vulnerable ranges and has an administrator-accessible interface reachable by remote attackers.
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 · scoped5.2.9.3492
Apply the vendor-supplied firmware updates (QTS 5.2.9.3492, QuTS hero h5.2.9.3499, h5.3.4.3500, or h6.0.0.3459 or later depending on model) to address the path traversal vulnerability.
QTS 5.2.9.3492+ (build 20260507) / QuTS hero h5.2.9.3499+ (build 20260514) / QuTS hero h5.3.4.3500+ (build 20260520) / QuTS hero h6.0.0.3459+ (build 20260409)
- 1. Back up all critical data on the QNAP device before proceeding with firmware update
- 2. Identify the current QTS or QuTS hero version from the QNAP admin console (System Administration > Firmware)
- 3. Download the appropriate fixed firmware from the official QNAP download center: QTS 5.2.9.3492 (build 20260507) or later, QuTS hero h5.2.9.3499 (build 20260514) or later, QuTS hero h5.3.4.3500 (build 20260520) or later, or QuTS hero h6.0.0.3459 (build 20260409) or later
- 4. Navigate to Control Panel > System Administration > Firmware Update and upload the downloaded firmware file
- 5. Allow the device to reboot during the update process - do not interrupt power
- 6. After reboot, verify the installed firmware version matches or exceeds the fixed version for your product line
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-24717 — 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-24717 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