CVE Intelligence
High

CVE-2025-9110 — QTS, QuTS hero

An exposure of sensitive system information to an unauthorized control sphere vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to read application data. We have already fixed the vulnerability in the following versions: QTS 5.2.8.3332 build 20251128 and later QuTS hero h5.2.8.3321 build 20251117 and later QuTS hero h5.3.1.3250 build 20250912 and later

Published Jan 2, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: qnap

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.5% (30-day exploitation probability)+6
  • 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.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.45%
ahead of 38% of scored CVEs · Oct 14, 2026
Affects
Qnap
Qts and 3 more
CVSS base
7.5
High · 4 source(s)

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.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Qnap Qts, Qnap Quts Hero, QNAP Systems Inc. QTS…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Qnap Qts version 5.2.0.2737-build_20240417version 5.2.7.3297-build_20251024version 5.2.7.3256-build_20250913version 5.2.6.3229-build_20250818version 5.2.6.3195-build_20250715version 5.2.5.3145-build_20250526version 5.2.4.3092-build_20250403version 5.2.4.3079-build_20250321
and 10 more version 5.2.4.3070-build_20250312version 5.2.3.3006-build_20250108version 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_20240601version 5.2.0.2744-build_20240424version 5.2.2.2950-build_20241114
Vulnerable NIST National Vulnerability Database
Qnap Quts Hero version h5.2.3.3006-build_20250108version h5.2.4.3070-build_20250312version h5.2.4.3079-build_20250321version h5.2.5.3138-build_20250519version h5.2.6.3195-build_20250715version h5.2.7.3256-build_20250913version h5.2.7.3297-build_20251024version h5.3.0.3115-build_20250430
and 12 more version h5.3.0.3145-build_20250530version h5.3.0.3192-build_20250716version h5.2.0.2782-build_20240601version h5.2.2.2952-build_20241116version h5.2.1.2940-build_20241105version h5.2.1.2929-build_20241025version h5.2.0.2860-build_20240817version h5.2.0.2851-build_20240808version h5.2.0.2823-build_20240711version h5.2.0.2802-build_20240620version h5.2.0.2789-build_20240607version h5.2.0.2737-build_20240417
Vulnerable NIST National Vulnerability Database
QNAP Systems Inc. QTS ≥ 5.2.x and < 5.2.8.3332 build 20251128 Vulnerable CVE Program (cve.org) e CISA ADP
QNAP Systems Inc. QuTS hero ≥ h5.2.x and < h5.2.8.3321 build 20251117≥ h5.3.x and < h5.3.1.3250 build 20250912 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
2.7 CVSS 4.0 Low — — security@qnapsecurity.com.tw via NIST National Vulnerability Database
2.7 CVSS 4.0 Low — — qnap via CVE Program (cve.org) e CISA ADP
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-497

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.45%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · qnap systems inc./qts, qnap systems inc./quts hero
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jan 2, 2026 · qnap

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

Qnap
every CVE for this vendor
CWE-497
other pages naming this weakness

Related CVEs (same products)

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-2025-9110 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.5 describes technical severity. EPSS 0.45% 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.