At a glance
As of November 6, 2026, 11 QNAP and Synology NAS vulnerabilities are listed in CISA's catalog of vulnerabilities exploited by attackers, including 9 used in ransomware. The most recent, CVE-2023-47565, was added on December 21, 2023.
Among the QNAP and Synology NAS vulnerabilities from the last four months in the NVD, the most severe is CVE-2026-80975 (score 7.8), published on September 11, 2026.
Are you affected? In the NAS interface: Control Panel → System → Firmware Update (QNAP) or Update & Restore (Synology).
Actively exploited
QNAP and Synology NAS vulnerabilities exploited by attackers
CISA's Known Exploited Vulnerabilities (KEV) catalog only lists vulnerabilities whose real-world exploitation has been confirmed. These are the first ones to patch.
| CVE | Product | Date added | Ransomware |
|---|---|---|---|
| CVE-2023-47565 QNAP VioStor NVR OS Command Injection Vulnerability. QNAP VioStar NVR contains an OS command injection vulnerability that allows authenticated users to execute commands via a network. | VioStor NVR | December 21, 2023 | Not reported |
| CVE-2022-27593 QNAP Photo Station Externally Controlled Reference Vulnerability. Certain QNAP NAS running Photo Station with internet exposure contain an externally controlled reference to a resource vulnerability which can allow an attacker to modify system files. This vulnerability was observed being utilized in a Deadbolt ransomware campaign. | Photo Station | September 8, 2022 | Yes |
| CVE-2019-7195 QNAP Photo Station Path Traversal Vulnerability. QNAP devices running Photo Station contain an external control of file name or path vulnerability allowing remote attackers to access or modify system files. | Photo Station | June 8, 2022 | Yes |
| CVE-2019-7194 QNAP Photo Station Path Traversal Vulnerability. QNAP devices running Photo Station contain an external control of file name or path vulnerability allowing remote attackers to access or modify system files. | Photo Station | June 8, 2022 | Yes |
| CVE-2019-7193 QNAP QTS Improper Input Validation Vulnerability. QNAP QTS contains an improper input validation vulnerability allowing remote attackers to inject code on the system. | QTS | June 8, 2022 | Yes |
| CVE-2019-7192 QNAP Photo Station Improper Access Control Vulnerability. QNAP NAS devices running Photo Station contain an improper access control vulnerability allowing remote attackers to gain unauthorized access to the system. | Photo Station | June 8, 2022 | Yes |
| CVE-2018-19953 QNAP NAS File Station Cross-Site Scripting Vulnerability. A cross-site scripting vulnerability affecting QNAP NAS File Station could allow remote attackers to inject malicious code. | Network Attached Storage (NAS) | May 24, 2022 | Yes |
| CVE-2018-19949 QNAP NAS File Station Command Injection Vulnerability. A command injection vulnerability affecting QNAP NAS File Station could allow remote attackers to run commands. | Network Attached Storage (NAS) | May 24, 2022 | Yes |
| CVE-2018-19943 QNAP NAS File Station Cross-Site Scripting Vulnerability. A cross-site scripting vulnerability affecting QNAP NAS File Station could allow remote attackers to inject malicious code. | Network Attached Storage (NAS) | May 24, 2022 | Yes |
| CVE-2020-2509 QNAP Network-Attached Storage (NAS) Command Injection Vulnerability. QNAP NAS devices contain a command injection vulnerability which could allow attackers to perform remote code execution. | QNAP Network-Attached Storage (NAS) | April 11, 2022 | Not reported |
| CVE-2021-28799 QNAP NAS Improper Authorization Vulnerability. QNAP NAS running HBS 3 contains an improper authorization vulnerability which can allow remote attackers to log in to a device. | Network Attached Storage (NAS) | March 31, 2022 | Yes |
New CVEs
QNAP and Synology NAS vulnerabilities from the last four months
- CVE-2026-80975published September 11, 2026In the Linux kernel, the following vulnerability has been resolved: mfd: qnap-mcu: keep the reply buffer alive past a command timeout qnap_mcu_exec() publishes an on-stack buffer to the receive path: unsigned char rx[QNAP_MCU_RX_BUFFER_SIZE]; ... reply->data = rx; reply->length = length; and qnap_mcu_receive_buf() writes into it from the serdev receive path, which runs out of flush_to_ldisc() and is not serialized against qnap_mcu_exec() at all. bus_lock cannot cover it, because qnap_mcu_exec() holds that mutex across wait_for_completion_timeout(). On a timeout qnap_mcu_exec() returns with reply->data still pointing at its own frame. A reply that arrives late, or an unsolicited message from the MCU, is then written into a stack frame that has been left, corrupting whatever runs next on that stack. The same applies when qnap_mcu_write() fails, since that path returns without touching the reply state either. Move the receive buffer into struct qnap_mcu. It is 37 bytes and the structure is devm_kzalloc()ed, so it lives as long as the driver, and a late write lands in memory that is still valid and is reinitialized by the next command. bus_lock keeps commands from sharing it. This deliberately does not clear reply->data or reply->length on the timeout path. Doing so races with qnap_mcu_receive_buf(), which reads both after its if (!reply->length) return size; check: clearing reply->data gives a NULL dereference, and clearing reply->length alone removes the reply->received == reply->length exit condition, so the copy loop runs until the uart chunk is consumed and overruns the buffer. Leaving both set keeps the write bounded by reply->length, which qnap_mcu_exec() has already checked against sizeof(mcu->rx).High7.8
Security news
QNAP and Synology NAS news
- November 6, 2026QNAP alerte sur des attaques exploitant la faille Plex2Shell ciblant ses appareils NASBleepingComputer ↗
- November 2, 2026Exploitation de vulnérabilités critiques dans les produits Synology révélant des risques d'exécution de code à distanceCERT-FR (ANSSI) ↗
A QNAP and Synology NAS vulnerability in your environment?
Patching a known CVE is not enough: our AI agents actually attack your applications and hand you proof of every open door.
