# CVE-2026-73630: SiYuan before v3.7.4 Information Disclosure via authFilePublishAccess

> An anonymous attacker can confirm the existence of hidden or forbidden documents and obtain publish-auth cookies for them via the authFilePublishAccess endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/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:** 14 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-4pjg-x8qj-33j5

## What is CVE-2026-73630?

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

### Official description

SiYuan before v3.7.4 contains an information disclosure vulnerability in the /api/filetree/authFilePublishAccess endpoint, which is registered with CheckAuth only and is reachable anonymously. The endpoint never sets a failure code, so its outcome is signalled entirely by the response message and by the presence of a Set-Cookie header, and these signals differ across access tiers. By submitting requests with an empty password for a candidate document identifier, an anonymous attacker can distinguish whether a document is public/nonexistent, password-protected, or exists at the hidden or forbidden tier, thereby confirming the existence of documents they are not permitted to access. Because hidden and forbidden entries store an empty password, such requests also cause the server to issue a publish-auth cookie for forbidden documents.

Weakness: CWE-203 (Observable Discrepancy)

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

2 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-20260731093152-c7522b8db586 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260731093152-c7522b8db586 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260731093152-c7522b8db586 or later.

## Is CVE-2026-73630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73630 is a medium-severity vulnerability in siyuan-note siyuan, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73630 in the wild and no public exploit code.

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

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

## Sources

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

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