QNAP QTS EUVD-2025-32465

Exploitation requires the attacker to already possess a QNAP operating-system administrator account (reflected in CVSS PR:H) - there is no unauthenticated path. Affected deployments are QTS 5.2.x prior to 5.2.6.3195 build 20250715 and QuTS hero h5.2.x prior to h5.2.6.3195 build 20250715; patched builds are not exploitable. The decisive limiting factor is the administrator-credential prerequisite, which confines realistic exploitation to insiders, credential-theft follow-on, or already-compromised admin sessions rather than opportunistic remote attack.

This is a genuine but low-priority issue. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N) and base score of 5.1 (Medium) hinge entirely on PR:H - exploitation requires the attacker to already hold a QNAP administrator account, which is explicitly confirmed by the description ('If a remote attacker gains an administrator account'). All exploitation-likelihood signals point low: EPSS is 0.05% (16th percentile), the CVE is NOT on CISA KEV, and no public exploit code is identified in the provided data - so this is 'no public exploit identified at time of analysis.' There is a notable internal conflict in the impact metrics: the description states the attacker can 'obtain secret data or modify memory' (implying confidentiality and integrity impact), yet the vendor 4.0 vector sets VC:N/VI:N and only VA:L (availability-low) - verify the true impact breakdown with QNAP's QSA-25-36 advisory, as the stated effects and scored metrics disagree. No SSVC decision data was supplied. Net: a high-privilege, low-probability, medium-severity bug - patch in routine cycles rather than as an emergency, since the admin-account prerequisite makes an unauthenticated internet-wide attack impossible.

An attacker who has already compromised or been granted a QNAP NAS administrator account sends crafted input containing format-string specifiers to an affected administrative function, causing the process to leak memory contents (secret data) or corrupt memory. No public exploit code is identified, and the network attack vector is gated entirely behind the required admin privileges, so this is a post-authentication escalation/disclosure primitive rather than an initial-access vector.