Is CVE-2026-68585 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-68585 being exploited in the wild.

How severe is CVE-2026-68585?

Medium severity, with a CVSS score of 5.8, published 3 September 2026.

Which products and versions are affected?

github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260721014951-ffde3b21eca4, SEMVER:introduced=0,fixed=0.0.0-20260721014951-ffde3b21eca4; SiYuan before 0.0.0-20260721014951-ffde3b21eca4.

Is there a fix for CVE-2026-68585?

Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721014951-ffde3b21eca4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-68585 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-68585?

Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-68585: SiYuan missing authorization in getBlockInfo metadata endpoint

Q: Is there a fix for CVE-2026-68585?

Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721014951-ffde3b21eca4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-68585 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-68585?

Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-68585 · Severity: medium · CVSS 5.8 · Published 2026-09-03

SiYuan is a popular open-source note-taking application. The `/api/block/getBlockInfo` endpoint fails to check whether a user has permission to access a document, exposing the document's title, location, and other metadata for documents an administrator has explicitly marked as hidden from public view. An attacker with network access to a SiYuan publish server can infer the existence and titles of private documents if they obtain a block identifier from within those documents.

Technologies: github.com/siyuan-note/siyuan/kernel (Go), SiYuan. Vendors: Go, SiYuan.

Quick answers

Is CVE-2026-68585 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-68585 being exploited in the wild.
How severe is CVE-2026-68585?: Medium severity, with a CVSS score of 5.8, published 3 September 2026.
Which products and versions are affected?: github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260721014951-ffde3b21eca4, SEMVER:introduced=0,fixed=0.0.0-20260721014951-ffde3b21eca4; SiYuan before 0.0.0-20260721014951-ffde3b21eca4.
Is there a fix for CVE-2026-68585?: Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721014951-ffde3b21eca4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-68585 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-68585?: Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721014951-ffde3b21eca4 or later
```
go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260721014951-ffde3b21eca4
```

Technical details

The vulnerability is a missing authorization check (CWE-862) in the `/api/block/getBlockInfo` API endpoint. The endpoint accepts a caller-supplied block ID, validates only its format, and returns the containing document's root metadata (box, path, rootID, rootTitle, rootChildID, rootIcon) with no `IsReadOnlyRoleContext` / publish-access filter applied. The equivalent endpoint `getDocInfo` implements the same access filter correctly, indicating the boundary is intentional but overlooked in `getBlockInfo`. Both endpoints are gated only by `CheckAuth`, making them reachable by anonymous users when publish auth is disabled and by publish `RoleReader` tokens. Exploitation requires a valid block ID from the target document; the endpoint does not enumerate arbitrary documents. The disclosed metadata is limited to document title and location metadata—not document content. The issue is fixed in version 0.0.0-20260721014951-ffde3b21eca4 by applying the same publish-access filter before returning metadata.

Affected products

SiYuan SiYuan before 0.0.0-20260721014951-ffde3b21eca4

Identifiers

CVE-2026-68585
GHSA-pm3w-vxp9-ccwc
GO-2026-6384

Timeline

2026-09-03: disclosed: Published to GitHub Advisory Database
2026-07-21: patched: Fix committed; patched version 0.0.0-20260721014951-ffde3b21eca4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.