<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 22:41:42 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-73607</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-73607</link>
      <description>&lt;p&gt;SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the /api/storage/getOutlineStorage endpoint that performs no authorization checks. Attackers can retrieve outline state including heading identifiers for any document by supplying its identifier, even for documents forbidden to the requester.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the /api/storage/getOutlineStorage endpoint that performs no authorization checks. Attackers can retrieve outline state including heading identifiers for any document by supplying its identifier, even for documents forbidden to the requester.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-73607</guid>
    </item>
    <item>
      <title>GHSA-53fp-9jmv-227g — SiYuan: Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlin…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-53fp-9jmv-227g</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;### Summary&lt;/p&gt;
&lt;p&gt;`/api/storage/getOutlineStorage` is registered with `CheckAuth` only and performs no authorization of any kind. Given a document identifier it returns that document&amp;#39;s stored outline state, regardless of the document&amp;#39;s publish tier.&lt;/p&gt;
&lt;p&gt;The two write endpoints for the same data, `setOutlineStorage` and `removeOutlineStorage`, both carry `CheckAdminRole` and `CheckReadonly`. Only the read path is unguarded.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Routes.** `kernel/api/router.go:103` on master, `:108` on the development branch:&lt;/p&gt;
&lt;p&gt;```go
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/getOutlineStorage&amp;#34;,    model.CheckAuth, getOutlineStorage)
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/setOutlineStorage&amp;#34;,    model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, setOutlineStorage)
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/removeOutlineStorage&amp;#34;, model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, removeOutlineStorage)
```&lt;/p&gt;
&lt;p&gt;**Handler.** `kernel/api/storage.go:466` on the development branch, `:469` on master, identical. It binds `docID` and calls `model.GetOutlineStorage(docID)`, which iterates the stored outline documents and returns the entry whose `DocID` matches. There is no filter function on this path at all: no `*gin.Context`, no publish-access check, no password check, no visibility check. The caller supplies the identifier and receives the payload.&lt;/p&gt;
&lt;p&gt;**What is stored.** `type OutlineDoc { DocID string; Data map[string]any }`. The client writes it from `app/src/layout/dock/Outline.ts:742`:&lt;/p&gt;
&lt;p&gt;```…&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;### Summary&lt;/p&gt;
&lt;p&gt;`/api/storage/getOutlineStorage` is registered with `CheckAuth` only and performs no authorization of any kind. Given a document identifier it returns that document&amp;#39;s stored outline state, regardless of the document&amp;#39;s publish tier.&lt;/p&gt;
&lt;p&gt;The two write endpoints for the same data, `setOutlineStorage` and `removeOutlineStorage`, both carry `CheckAdminRole` and `CheckReadonly`. Only the read path is unguarded.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Routes.** `kernel/api/router.go:103` on master, `:108` on the development branch:&lt;/p&gt;
&lt;p&gt;```go
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/getOutlineStorage&amp;#34;,    model.CheckAuth, getOutlineStorage)
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/setOutlineStorage&amp;#34;,    model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, setOutlineStorage)
ginServer.Handle(&amp;#34;POST&amp;#34;, &amp;#34;/api/storage/removeOutlineStorage&amp;#34;, model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, removeOutlineStorage)
```&lt;/p&gt;
&lt;p&gt;**Handler.** `kernel/api/storage.go:466` on the development branch, `:469` on master, identical. It binds `docID` and calls `model.GetOutlineStorage(docID)`, which iterates the stored outline documents and returns the entry whose `DocID` matches. There is no filter function on this path at all: no `*gin.Context`, no publish-access check, no password check, no visibility check. The caller supplies the identifier and receives the payload.&lt;/p&gt;
&lt;p&gt;**What is stored.** `type OutlineDoc { DocID string; Data map[string]any }`. The client writes it from `app/src/layout/dock/Outline.ts:742`:&lt;/p&gt;
&lt;p&gt;```…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-53fp-9jmv-227g</guid>
    </item>
  </channel>
</rss>
