CVE-2026-41544 QNAP Systems Inc. CVE debrief

Who should care

Defenders responsible for QcalAgent deployments should assess exposure and apply the vendor-provided fix to prevent potential exploitation. The vulnerability can lead to arbitrary file moves, Docker escape, and host RCE, and allows a remote attacker with a user account to read unexpected files or system data. Verification of QcalAgent version and application of the fix is necessary to prevent exploitation.

Why it matters

Defenders should prioritize verifying exposure and applying the vendor-provided fix, as the vulnerability can lead to arbitrary file moves, Docker escape, and host RCE, and allows a remote attacker with a user account to read unexpected files or system data.

• Potential arbitrary file moves, Docker escape, and host RCE
• Possible reading of unexpected files or system data
• Verification of QcalAgent version and application of the fix is necessary

Technical summary

A path traversal vulnerability in the /calapi/renameUpload endpoint of QcalAgent can allow a remote attacker with a user account to read unexpected files or system data. The vulnerability has been fixed in QcalAgent version 1.1.10 and later. The vulnerability can lead to arbitrary file moves, Docker escape, and host RCE. Defenders should prioritize verifying exposure and applying the vendor-provided fix. The CVE record and source item provide details on the vulnerability, affected versions, and fixed versions. However, there is limited information on potential exploitation or victim impact.

Defensive priority

Defenders should prioritize verifying exposure and applying the vendor-provided fix, as the vulnerability can lead to arbitrary file moves, Docker escape, and host RCE.

Recommended defensive actions

• Verify QcalAgent version and apply the fix (upgrade to version 1.1.10 or later)
• Review and restrict access to the /calapi/renameUpload endpoint
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed versions. However, there is limited information on potential exploitation or victim impact. Defenders should verify exposure and apply the vendor-provided fix. The vulnerability can lead to arbitrary file moves, Docker escape, and host RCE. There is no information on known or unknown affected scope. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.