ZeroDay Findings
Sign inSign up

Findings

CVE-2025-29897

A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central.

Published Oct 15, 2026 · updated Oct 15, 2026 · QNAP Systems Inc. Qsync Central

A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central. 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 version: Qsync Central 5.0.0.4 and later

Timeline

Detection, updates, and resolution for this record.

  1. Oct 15, 2026 · NIST NVD

    Detected

    A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central. 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 version: Qsync Central 5.0.0.4 and later

  2. Oct 15, 2026 · NIST NVD

    Updated

    A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central. 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 version: Qsync Central 5.0.0.4 and later

Affected

  • vendor QNAP Systems Inc. Qsync Centralversion unspecified

Sources

  • CIRCL Vulnerability LookupCVE-2025-29897

    A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central. 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 v

    vulnerability.circl.lu
  • CVE.orgCVE-2025-29897

    Official CVE identifier

    cve.org
  • NIST NVDCVE-2025-29897

    A buffer copy without checking size of input vulnerability has been reported to affect Qsync Central. 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

    nvd.nist.gov

References