CVE-2024-14026 — QTS, QuTS hero
A command injection vulnerability has been reported to affect several QNAP operating system versions. If an attacker gains local network access who have also gained a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.3.3006 build 20250108 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.3.3006 build 20250108 and later
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Qnap Qts, Qnap Quts Hero, QNAP Systems Inc. QTS…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Qnap | Qts |
version 5.1.5.2679-build_20240219version 5.2.2.2950-build_20241114version 5.2.1.2930-build_20241025version 5.2.0.2860-build_20240817version 5.2.0.2851-build_20240808version 5.2.0.2823-build_20240711version 5.2.0.2802-build_20240620version 5.2.0.2782-build_20240601 and 15 moreversion 5.2.0.2744-build_20240424version 5.2.0.2737-build_20240417version 5.1.8.2823-build_20240712version 5.1.7.2770-build_20240520version 5.1.6.2722-build_20240402version 5.1.5.2645-build_20240116version 5.1.4.2596-build_20231128version 5.1.3.2578-build_20231110version 5.1.2.2533-build_20230926version 5.1.1.2491-build_20230815version 5.1.0.2466-build_20230721version 5.1.0.2444-build_20230629version 5.1.0.2418-build_20230603version 5.1.0.2399-build_20230515version 5.1.0.2348-build_20230325 |
Vulnerable | NIST National Vulnerability Database |
| Qnap | Quts Hero |
version h5.1.8.2823-build_20240712version h5.2.0.2782-build_20240601version h5.2.0.2737-build_20240417version h5.1.7.2770-build_20240520version h5.1.7.2794-build_20240613version h5.1.7.2788-build_20240607version h5.2.1.2940-build_20241105version h5.2.0.2789-build_20240607 and 17 moreversion h5.2.0.2802-build_20240620version h5.2.0.2823-build_20240711version h5.2.0.2851-build_20240808version h5.2.0.2860-build_20240817version h5.2.1.2929-build_20241025version h5.1.6.2734-build_20240414version h5.1.5.2680-build_20240220version h5.1.5.2647-build_20240118version h5.1.4.2596-build_20231128version h5.1.3.2578-build_20231110version h5.1.2.2534-build_20230927version h5.1.1.2488-build_20230812version h5.1.0.2466-build_20230721version h5.1.0.2453-build_20230708version h5.1.0.2424-build_20230609version h5.1.0.2409-build_20230525version h5.2.2.2952-build_20241116 |
Vulnerable | NIST National Vulnerability Database |
| QNAP Systems Inc. | QTS | ≥ 5.2.x and < 5.2.3.3006 build 20250108≥ 5.1.x and < 5.1.9.2954 build 20241120 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| QNAP Systems Inc. | QuTS hero | ≥ h5.1.x and < h5.1.9.2954 build 20241120≥ h5.2.x and < h5.2.3.3006 build 20250108 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.0 | CVSS 4.0 | Low | — | — | security@qnapsecurity.com.tw via NIST National Vulnerability Database |
| 2.0 | CVSS 4.0 | Low | — | — | qnap via CVE Program (cve.org) e CISA ADP |
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.64%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · qnap systems inc./qts, qnap systems inc./quts hero
- SSVC assessment updated
- Record published
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-24719 QTS, QuTS hero Jun 10, 2026
- Medium CVE-2026-24717 QTS, QuTS hero Jun 10, 2026
- High CVE-2026-24716 QTS, QuTS hero Jun 10, 2026
- High CVE-2026-22893 QTS, QuTS hero Jun 10, 2026
- High CVE-2025-66281 QTS, QuTS hero Jun 10, 2026
- High CVE-2025-66273 QTS, QuTS hero Jun 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-14026 is "QTS, QuTS hero", rated High. It affects Qts (Qnap); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.64% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.