Skip to main content
Mallory
HighVulnerability

CVE-2025-66273: Command Injection in QNAP QTS and QuTS hero

Published Jun 10, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v4
EPSS1.1%65th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
QNAP Systems
IdentifiersCVE-2025-66273CWE-78 · Improper Neutralization of Special…

CVE-2025-66273 is a command injection vulnerability affecting several QNAP operating system versions, including QTS and QuTS hero releases. The flaw allows an authenticated administrator to inject arbitrary system commands through a username parameter. Exploitation is possible over the network and does not require user interaction once valid administrator access has been obtained. Successful exploitation results in arbitrary command execution on the affected NAS or appliance.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker with administrator privileges to execute arbitrary system commands on the affected device. This can lead to full compromise of the vulnerable system, including unauthorized access to data, modification or destruction of stored information, service disruption, and use of the device as a pivot for further activity within the environment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of administrative interfaces, restrict administrator access to trusted networks and accounts only, keep management services off the public internet where feasible, and monitor for suspicious administrative activity. Apply least-privilege administration practices and rotate or revoke potentially exposed administrator credentials to reduce the likelihood of prerequisite account compromise.

Remediation

Patch, then assume compromise.

Upgrade affected systems to a fixed release. QNAP states the vulnerability is fixed in QTS 5.2.9.3410 build 20260214 and later, QuTS hero h5.2.9.3410 build 20260214 and later, QuTS hero h5.3.4.3500 build 20260520 and later, and QuTS hero h6.0.0.3397 build 20260206 and later. More broadly, QNAP also advises updating to the latest available firmware and applying vendor-issued security patches promptly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
QNAP SystemsQtsapplication
QNAP SystemsQuts Heroapplication
FAQ

Frequently asked questions

Is CVE-2025-66273 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-66273 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-66273?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-66273.
Is there a patch for CVE-2025-66273?
Upgrade affected systems to a fixed release. QNAP states the vulnerability is fixed in QTS 5.2.9.3410 build 20260214 and later, QuTS hero h5.2.9.3410 build 20260214 and later, QuTS hero h5.3.4.3500 build 20260520 and later, and QuTS hero h6.0.0.3397 build 20260206 and later.
What products are affected by CVE-2025-66273?
QNAP Systems Qts and QNAP Systems Quts Hero.
How severe is CVE-2025-66273?
CVE-2025-66273 has a CVSS v4 score of 8.6 (High) and an EPSS score of 1.1% (65th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.