cve.bz

CVE-2025-52864 qnap: Classic Buffer Overflow

1.3 lowEPSS 0.4%

Low (1.3) in qnap. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A buffer overflow vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following versions: QTS 5.2.7.3256 build 20250913 and later QuTS hero h5.2.7.3256 build 20250913 and later QuTS hero h5.3.0.3192 build 20250716 and later

Severity

CVSS 4.0

1.3 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:U

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-01-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-52864 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-52864?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-52864?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-52864 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-52864

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-52864](https://cve.bz/cve/badge/CVE-2025-52864.svg)](https://cve.bz/cve/CVE-2025-52864)

HTML:

<a href="https://cve.bz/cve/CVE-2025-52864"><img src="https://cve.bz/cve/badge/CVE-2025-52864.svg" alt="CVE-2025-52864"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
QNAP Systems Inc. QTSfrom 5.2.x before 5.2.7.3256 build 20250913
QNAP Systems Inc. QuTS herofrom h5.2.x before h5.2.7.3256 build 20250913
QNAP Systems Inc. QuTS herofrom h5.3.x before h5.3.0.3192 build 20250716

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-120 (13).

References

Check your stackJSON