# CVE-2026-59854: SiYuan: Incomplete IsSensitivePath denylist: globalCopyFiles reads home-dir credential dotfiles into the workspace

> An authenticated user can copy sensitive home-directory credential files into the workspace via an incomplete path denylist, leading to credential exposure.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-vmm8-3ccv-ppvw

## What is CVE-2026-59854?

CVE-2026-59854 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.1, POST /api/file/globalCopyFiles accepts attacker-supplied absolute source paths and relies on util.IsSensitivePath in kernel/util/path.go, whose denylist misses common home-directory credential files such as .git-credentials, .netrc, .pgpass, .kube/config, .docker/config.json, and .gnupg, allowing an authenticated administrator or API-token user to copy those files into the workspace and exfiltrate them through the file API. This issue is fixed in versions 3.7.1-alpha.2 and 3.7.1.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2026-59854 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59854 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59854 in the wild and no public exploit code.

Affected product: siyuan-note siyuan. 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-59854/ (Markdown: https://insights.sbomify.com/CVE-2026-59854/index.md)
```

## Sources

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

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