Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

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) <= 3.7.2; SiYuan <= 3.7.2.

Is there a fix for This vulnerability?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is This vulnerability attacked?

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

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.

Siyuan session cookie signing key disclosure via /api/system/getConf

Q: Is there a fix for This vulnerability?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is This vulnerability attacked?

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

Q: Am I affected?

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.

Severity: high · CVSS 8.6 · Published 2026-08-12

Siyuan is a note-taking application with network-accessible APIs. An unauthenticated attacker can retrieve the server's session cookie signing key from the /api/system/getConf endpoint, allowing them to forge valid session cookies and impersonate any user or administrator on the system. This cryptographic secret cannot be changed without invalidating all active user sessions.

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

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: 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) <= 3.7.2; SiYuan <= 3.7.2.
Is there a fix for This vulnerability?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?: It is attacked over the network, in a web application.
Am I affected?: 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.

Technical details

The /api/system/getConf endpoint is protected only by CheckAuth middleware and returns the Conf.CookieKey field in its response body to anonymous users when Publish.Auth.Enable is false or to any publish RoleReader account. This key is used to sign the server's session cookies via gorilla/securecookie HMAC. The vulnerability exists because CookieKey is not filtered by the HideConfSecret() or FilterConfByPublishIgnore() masking functions in the response path, despite being explicitly stripped by the guarded exportConf endpoint. An attacker can call POST /api/system/getConf with no credentials to obtain the cleartext signing key, then use it to forge valid session cookies. On instances without an access-auth code configured, this enables authentication as a privileged user. The disclosed key is a persistent cryptographic secret that cannot be remediated without invalidating all active sessions.

Affected products

Siyuan Note Siyuan <= 3.7.2

Timeline

2026-07-25: disclosed
2026-08-12: advisory
2026-09-04: other: This advisory (GHSA-hg4j-w33m-p7g4) was withdrawn as a duplicate of GHSA-34fj-mwm6-fjfg

References

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