<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 12:14:48 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-72794</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-72794</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-72794</guid>
    </item>
    <item>
      <title>GHSA-34fj-mwm6-fjfg — SiYuan: The session-cookie signing key (Conf.CookieKey) is returned to anonymous readers by /api/system/getConf</title>
      <link>https://db.gcve.eu/vuln/ghsa-34fj-mwm6-fjfg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/siyuan-note/siyuan/kernel&lt;/p&gt;
&lt;p&gt;**CVE:** This vulnerability corresponds to [CVE-2026-72794](https://nvd.nist.gov/vuln/detail/CVE-2026-72794).&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`/api/system/getConf` returns `Conf.CookieKey`, the key used to sign the server&amp;#39;s session cookies in its response body. The endpoint is registered with `CheckAuth` only, so the field reaches the publish `RoleReader` token and the anonymous account when `Publish.Auth.Enable` is `false`.&lt;/p&gt;
&lt;p&gt;The configuration-export endpoint in the same file strips this exact field before returning config, so the project already treats it as secret. The reader-facing masking path does not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;| Item | Detail |
|---|---|
| Route | `kernel/api/router.go:70` `POST /api/system/getConf` → `model.CheckAuth` → `getConf` |
| Middleware | `CheckAuth` only — no `CheckReadonly`, no `CheckAdminRole` |
| Leaked field | `AppConf.CookieKey`, serialized as `cookieKey` |
| Purpose of the field | Signing key for the `siyuan` session cookie |&lt;/p&gt;
&lt;p&gt;**The field survives every stage of the masking chain.** `getConf` masks through `GetMaskedConf()` → `HideConfSecret()` (non-administrators) → `FilterConfByPublishIgnore()` (readers) → the browser-side System-path strip. `CookieKey` is removed by none of them:&lt;/p&gt;
&lt;p&gt;- `GetMaskedConf` masks `UserData`, `MCPOAuth` and `AccessAuthCode` only.
- `HideConfSecret` nulls `AI`, `Api`, `Flashcard`, `ServerAddrs`, `Publish`, `Repo`, `Sync`, `Secrets`, `Variables` and the System paths. It contains no reference to `CookieKey`.
- `FilterConfByPublishIgnore` touc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/siyuan-note/siyuan/kernel&lt;/p&gt;
&lt;p&gt;**CVE:** This vulnerability corresponds to [CVE-2026-72794](https://nvd.nist.gov/vuln/detail/CVE-2026-72794).&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`/api/system/getConf` returns `Conf.CookieKey`, the key used to sign the server&amp;#39;s session cookies in its response body. The endpoint is registered with `CheckAuth` only, so the field reaches the publish `RoleReader` token and the anonymous account when `Publish.Auth.Enable` is `false`.&lt;/p&gt;
&lt;p&gt;The configuration-export endpoint in the same file strips this exact field before returning config, so the project already treats it as secret. The reader-facing masking path does not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;| Item | Detail |
|---|---|
| Route | `kernel/api/router.go:70` `POST /api/system/getConf` → `model.CheckAuth` → `getConf` |
| Middleware | `CheckAuth` only — no `CheckReadonly`, no `CheckAdminRole` |
| Leaked field | `AppConf.CookieKey`, serialized as `cookieKey` |
| Purpose of the field | Signing key for the `siyuan` session cookie |&lt;/p&gt;
&lt;p&gt;**The field survives every stage of the masking chain.** `getConf` masks through `GetMaskedConf()` → `HideConfSecret()` (non-administrators) → `FilterConfByPublishIgnore()` (readers) → the browser-side System-path strip. `CookieKey` is removed by none of them:&lt;/p&gt;
&lt;p&gt;- `GetMaskedConf` masks `UserData`, `MCPOAuth` and `AccessAuthCode` only.
- `HideConfSecret` nulls `AI`, `Api`, `Flashcard`, `ServerAddrs`, `Publish`, `Repo`, `Sync`, `Secrets`, `Variables` and the System paths. It contains no reference to `CookieKey`.
- `FilterConfByPublishIgnore` touc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-34fj-mwm6-fjfg</guid>
    </item>
  </channel>
</rss>
