# CVE-2026-41541: Symlink creation in qsyncsrv.cgi

> Remote attackers with user accounts can exploit symlink following in Qsync Central to compromise system security by reading or modifying arbitrary files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-wfqp-r282-w463

## What is CVE-2026-41541?

CVE-2026-41541 is a medium-severity path traversal vulnerability in QNAP Systems Inc. Qsync Central, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An unix symbolic link (symlink) following vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to compromise the security of the system.

We have already fixed the vulnerability in the following version:
Qsync Central 5.0.0.7 and later
Qsync Central 5.1.0.3 and later
Qsync Central 5.2.0.5 and later
Qsync Central 5.3.0.2 and later

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-41541?


## How do I fix CVE-2026-41541?

No fix has been published for CVE-2026-41541 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41541 being exploited?

There is no known exploitation of CVE-2026-41541 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41541 and fix it if it is affected.

What it is: CVE-2026-41541 is a medium-severity path traversal vulnerability in QNAP Systems Inc. Qsync Central, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41541 in the wild and no public exploit code.

Affected product: QNAP Systems Inc. Qsync Central. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41541/ (Markdown: https://insights.sbomify.com/CVE-2026-41541/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41541
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41541
- OSV: https://osv.dev/vulnerability/CVE-2026-41541

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41541/
Summaries are generated and may contain mistakes; the official description above is the record.