GO · SEPTEMBER 2026 · EARLY WARNING

SiYuan Package Vulnerability: Session-Cookie Signing Key Exposure

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
siyuan (go)
Affected versions
<= 0.0.0-20260313024916-fd6526133bb3
Patched version
Not yet available
CVE-2026-72794GHSA-34FJ-MWM6-FJFG

An early warning has been issued regarding a vulnerability in the SiYuan package. The session-cookie signing key (Conf.CookieKey) is reportedly exposed to anonymous readers via the /api/system/getConf endpoint.

What happened

The SiYuan package, specifically versions up to and including 0.0.0-20260313024916-fd6526133bb3, appears to expose the session-cookie signing key (Conf.CookieKey) to unauthorized users. This key is critical as it is used to sign the server's session cookies. The exposure occurs through the /api/system/getConf endpoint, which returns the key to any reader, regardless of their authorization status.

Additionally, there are reports of other vulnerabilities in the SiYuan package. These include the exposure of database view structures to anonymous readers via the /api/av/getAttributeViewFieldViews endpoint and the disclosure of the private document tree to anonymous readers due to a missing publish-access filter on the HPath/path-resolution endpoints.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If siyuan is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are potentially affected if you are using the SiYuan package version 0.0.0-20260313024916-fd6526133bb3 or earlier.

What should I do right now?

Review and update your SiYuan package to ensure the session-cookie signing key is not exposed to unauthorized users. Monitor the primary sources for updates on patched versions and additional mitigation steps.

Has this been exploited in the wild?

There is no confirmed report of this vulnerability being exploited in the wild at this time.

Are there any official fixes available?

No official fix has been published yet. Monitor the primary sources for updates on patched versions.

Sources

Join the 0Day waitlist →

← Back to all threats