What is GHSA-hg4j-w33m-p7g4?

GHSA-hg4j-w33m-p7g4 is a security advisory published by GitHub Security Advisories with Critical severity. Duplicate Advisory: The session-cookie signing key (Conf.CookieKey) is returned to anonymous readers by /api/system/getConf

Why does GHSA-hg4j-w33m-p7g4 have no CVE ID yet?

GitHub Security Advisories published this advisory directly to customers before NVD assigned a CVE ID. This is the embargo-window disclosure pattern — vendors notify customers on day 0; NVD's public record follows days to weeks later.

What is the CVSS v3 score of GHSA-hg4j-w33m-p7g4?

GHSA-hg4j-w33m-p7g4 has a CVSS v3 base score of 8.6, published by GitHub Security Advisories.

Which products are affected by GHSA-hg4j-w33m-p7g4?

GHSA-hg4j-w33m-p7g4 affects 1 product, including: go/github.com/siyuan-note/siyuan/kernel:\u003c= 3.7.2.

⚠ Withdrawn by GitHub Security Advisories

Withdrawn: September 4, 2026

GHSA-hg4j-w33m-p7g4CriticalCVSS 8.6Disclosed before NVD

Duplicate Advisory: The session-cookie signing key (Conf.CookieKey) is returned to anonymous readers by /api/system/getConf

Vendor

GitHub Security Advisories

Published

August 12, 2026

Last Modified

September 4, 2026

📋 Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-34fj-mwm6-fjfg. This link is maintained to preserve external references.

Original Description

siyuan versions before v3.7.4 expose the session cookie signing key through the /api/system/getConf endpoint to unauthenticated users in publish mode. Attackers can retrieve the CookieKey value and forge valid session cookies to impersonate users or gain administrative access.

🎯 Affected products1

go/github.com/siyuan-note/siyuan/kernel:<= 3.7.2

🔗 References (4)

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-34fj-mwm6-fjfg
https://nvd.nist.gov/vuln/detail/CVE-2026-72794
https://www.vulncheck.com/advisories/siyuan-before-session-cookie-key-disclosure-via-getconf
https://github.com/advisories/GHSA-hg4j-w33m-p7g4