# CVE-2026-68585: SiYuan before v3.7.3 Metadata Disclosure via getBlockInfo

> Attackers can retrieve metadata of unpublished documents via the getBlockInfo API, exposing titles and paths to unauthorized users.

- **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:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-pm3w-vxp9-ccwc, GO-2026-6384

## What is CVE-2026-68585?

CVE-2026-68585 is a medium-severity vulnerability in siyuan-note siyuan, published on 3 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.3 contain a metadata disclosure vulnerability in the /api/block/getBlockInfo endpoint that returns document root metadata including title for publish-forbidden documents without publish-access checks. Anonymous readers or publish RoleReader tokens can supply a block ID to retrieve the title, notebook, path, root ID, and icon of documents administrators marked as excluded from publishing.

Weakness: CWE-862 (Missing Authorization)

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721014951-ffde3b21eca4 or later.

## Is CVE-2026-68585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68585 is a medium-severity vulnerability in siyuan-note siyuan, published on 3 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-68585 exists.

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

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

## Sources

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

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