# CVE-2026-72802: SiYuan before v3.7.4 Information Disclosure via resolveAssetPath

> Attackers can obtain absolute filesystem paths and OS usernames by exploiting the resolveAssetPath endpoint in SiYuan.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-jv8v-xq2h-657v, GO-2026-6398

## What is CVE-2026-72802?

CVE-2026-72802 is a medium-severity vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the resolveAssetPath endpoint that returns absolute filesystem paths unmodified to CheckAuth-only requests. Attackers can harvest relative asset paths from published documents and submit them to resolveAssetPath to obtain the server's absolute workspace path, disclosing the operating-system username and installation layout.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724095509-eee3410aa131 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724095509-eee3410aa131 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260724095509-eee3410aa131 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724095509-eee3410aa131 or later.

## Is CVE-2026-72802 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72802 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72802 is a medium-severity vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72802 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724095509-eee3410aa131
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724095509-eee3410aa131
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260724095509-eee3410aa131

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-72802/ (Markdown: https://insights.sbomify.com/CVE-2026-72802/index.md)
```

## Sources

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

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