CVE-2026-41539
Last modified
CVE-2026-41539 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. A cross-site scripting (XSS) vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to bypass security mechanisms or read application data. We have already fixed the vulnerability in the following versions: QTS 5.2.9.3492 build 20260507 and later QuTS hero h5.2.9.3499 build 20260514 and later QuTS hero h5.3.4.3500 build 20260520 and later QuTS hero h6.0.0.3500 build 20260520 and later. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
A cross-site scripting (XSS) vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to bypass security mechanisms or read application data. We have already fixed the vulnerability in the following versions: QTS 5.2.9.3492 build 20260507 and later QuTS hero h5.2.9.3499 build 20260514 and later QuTS hero h5.3.4.3500 build 20260520 and later QuTS hero h6.0.0.3500 build 20260520 and later
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Qnap | Qts | 5.2.0.2737 | Build 20240417 |
| Qnap | Qts | 5.2.0.2744 | Build 20240424 |
| Qnap | Qts | 5.2.0.2782 | Build 20240601 |
| Qnap | Qts | 5.2.0.2802 | Build 20240620 |
| Qnap | Qts | 5.2.0.2823 | Build 20240711 |
| Qnap | Qts | 5.2.0.2851 | Build 20240808 |
| Qnap | Qts | 5.2.0.2860 | Build 20240817 |
| Qnap | Qts | 5.2.1.2930 | Build 20241025 |
| Qnap | Qts | 5.2.2.2950 | Build 20241114 |
| Qnap | Qts | 5.2.3.3006 | Build 20250108 |
| Qnap | Qts | 5.2.4.3070 | Build 20250312 |
| Qnap | Qts | 5.2.4.3079 | Build 20250321 |
| Qnap | Qts | 5.2.4.3092 | Build 20250403 |
| Qnap | Qts | 5.2.5.3145 | Build 20250526 |
| Qnap | Qts | 5.2.6.3195 | Build 20250715 |
| Qnap | Qts | 5.2.6.3229 | Build 20250818 |
| Qnap | Qts | 5.2.7.3256 | Build 20250913 |
| Qnap | Qts | 5.2.7.3297 | Build 20251024 |
| Qnap | Qts | 5.2.8.3332 | Build 20251128 |
| Qnap | Qts | 5.2.8.3350 | Build 20251216 |
| Qnap | Qts | 5.2.8.3359 | Build 20251225 |
| Qnap | Qts | 5.2.9.3410 | Build 20260214 |
| Qnap | Qts | 5.2.9.3451 | Build 20260327 |
| Qnap | Quts Hero | h5.2.0.2737 | Build 20240417 |
| Qnap | Quts Hero | h5.2.0.2782 | Build 20240601 |
| Qnap | Quts Hero | h5.2.0.2789 | Build 20240607 |
| Qnap | Quts Hero | h5.2.0.2802 | Build 20240620 |
| Qnap | Quts Hero | h5.2.0.2823 | Build 20240711 |
| Qnap | Quts Hero | h5.2.0.2851 | Build 20240808 |
| Qnap | Quts Hero | h5.2.0.2860 | Build 20240817 |
| Qnap | Quts Hero | h5.2.1.2929 | Build 20241025 |
| Qnap | Quts Hero | h5.2.1.2940 | Build 20241105 |
| Qnap | Quts Hero | h5.2.2.2952 | Build 20241116 |
| Qnap | Quts Hero | h5.2.3.3006 | Build 20250108 |
| Qnap | Quts Hero | h5.2.4.3070 | Build 20250312 |
| Qnap | Quts Hero | h5.2.4.3079 | Build 20250321 |
| Qnap | Quts Hero | h5.2.5.3138 | Build 20250519 |
| Qnap | Quts Hero | h5.2.6.3195 | Build 20250715 |
| Qnap | Quts Hero | h5.2.7.3256 | Build 20250913 |
| Qnap | Quts Hero | h5.2.7.3297 | Build 20251024 |
| Qnap | Quts Hero | h5.2.8.3321 | Build 20251117 |
| Qnap | Quts Hero | h5.2.8.3350 | Build 20251216 |
| Qnap | Quts Hero | h5.2.8.3359 | Build 20251225 |
| Qnap | Quts Hero | h5.2.9.3410 | Build 20260214 |
| Qnap | Quts Hero | h5.2.9.3492 | Build 20260507 |
| Qnap | Quts Hero | h5.3.0.3115 | Build 20250430 |
| Qnap | Quts Hero | h5.3.0.3145 | Build 20250530 |
| Qnap | Quts Hero | h5.3.0.3192 | Build 20250716 |
| Qnap | Quts Hero | h5.3.1.3250 | Build 20250912 |
| Qnap | Quts Hero | h5.3.1.3292 | Build 20251024 |
Showing 50 of 56 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-41539?
How severe is CVE-2026-41539?
How do I fix CVE-2026-41539?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-41524Brave CMS is an open-source CMS. Prior to commit 6c56603, pa…8.7
- CVE-2026-41525KDE Dolphin before 25.12.3 allows applications in a Flatpak …6.5
- CVE-2026-41526In KDE KCoreAddons before 6.25, KShell::quoteArgs is intende…7.8
- CVE-2026-41527KDE Kleopatra before 26.08.0 on Windows allows local users t…6.9
- CVE-2026-4153GIMP PSP File Parsing Heap-based Buffer Overflow Remote Code…7.8
- CVE-2026-41530The automatic folder creation feature of Lhaz and Lhaz+ prov…4.6
- CVE-2026-4154GIMP XPM File Parsing Integer Overflow Remote Code Execution…7.8
- CVE-2026-4155ChargePoint Home Flex Inclusion of Sensitive Information in …7.5
- CVE-2026-41551A vulnerability has been identified in ROS# (All versions < …9.3
- CVE-2026-41552PDF Export Module used in DHTMLX's products Gantt and Schedu…7.5
- CVE-2026-41553PDF Export Module used in DHTMLX's products Gantt and Schedu…10
- CVE-2026-41554Improper Neutralization of Input During Web Page Generation …7.1
Are you affected by CVE-2026-41539?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
