Is CVE-2026-72794 exploited in the wild?

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

How severe is CVE-2026-72794?

High severity, with a CVSS score of 8.6, published 12 August 2026.

Which products and versions are affected?

github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260725123945-77421530be4a, SEMVER:introduced=0,fixed=0.0.0-20260725123945-77421530be4a; SiYuan < 0.0.0-20260725123945-77421530be4a.

Is there a fix for CVE-2026-72794?

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

How is CVE-2026-72794 attacked?

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

Am I affected by CVE-2026-72794?

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-72794: SiYuan session-cookie signing key disclosure in /api/system/getConf

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

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

Q: How is CVE-2026-72794 attacked?

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

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

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-72794 · Severity: high · CVSS 8.6 · Published 2026-08-12

SiYuan is a note-taking application that uses a cryptographic signing key to secure user session cookies. The `/api/system/getConf` API endpoint incorrectly exposes this signing key in its response to anonymous users and readers in publish mode. An attacker with access to this key can forge valid session cookies to impersonate users, potentially including administrators if no access code is configured, without needing to compromise any user credentials.

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

Quick answers

Is CVE-2026-72794 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-72794 being exploited in the wild.
How severe is CVE-2026-72794?: High severity, with a CVSS score of 8.6, published 12 August 2026.
Which products and versions are affected?: github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260725123945-77421530be4a, SEMVER:introduced=0,fixed=0.0.0-20260725123945-77421530be4a; SiYuan < 0.0.0-20260725123945-77421530be4a.
Is there a fix for CVE-2026-72794?: Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260725123945-77421530be4a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-72794 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-72794?: 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-20260725123945-77421530be4a or later
```
go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260725123945-77421530be4a
```

Technical details

The vulnerability is an insufficiently protected credentials disclosure (CWE-522) in the configuration retrieval endpoint. The `/api/system/getConf` route is protected only by `CheckAuth` middleware, allowing access by publish-mode readers and anonymous users when `Publish.Auth.Enable` is false. The leaked field `AppConf.CookieKey` is a live HMAC secret used to sign the `siyuan` session cookie via `gorilla/securecookie`. The masking chain (`GetMaskedConf` → `HideConfSecret` → `FilterConfByPublishIgnore`) fails to remove this field at any stage, unlike the `exportConf` endpoint which explicitly clears both `CookieKey` and `NotebookCrypto`. An attacker obtaining this key can use `gin-contrib/sessions/cookie.NewStore` logic to forge valid session cookies. Escalation to administrator requires either no access-auth code configured or possession of the matching `AccessAuthCode`. The key is persistent and rotation invalidates all sessions, making this a critical secret disclosure. A patch was released in version 0.0.0-20260725123945-77421530be4a.

Affected products

siyuan-note SiYuan < 0.0.0-20260725123945-77421530be4a

Identifiers

CVE-2026-72794
GHSA-34fj-mwm6-fjfg
GO-2026-6420

Timeline

2026-09-04: disclosed: Published to GitHub Advisory Database
2026-07-25: patched: Patch version 0.0.0-20260725123945-77421530be4a released

References

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