Skip to content

← Actionable
Medium, CVSS 5.8amended

SiYuan: The publish filter for local storage returns the administrator's entire storage map with only three keys sanitized

GHSA-xp3q-r38w-vgqm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/siyuan-note/siyuan/kernel 0.0.0-20260729005258-4daee87d4152), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Relationship to GHSA-hgfg-j9pg-43xw That advisory concerned the administrator's live UI layout, and commit 63c7d5474 resolved it by removing FilterUILayoutByPublishIgnore and nulling Conf.UILayout for readers. That fix is correct and complete for the live layout. This report concerns a different endpoint, a different filter function and a different storage backing. /api/storage/getLocalStorage reads data/storage/local.json rather than Conf.UILayout, and its filter FilterLocalStorageByPublishAccess was not touched by that commit. The consequence is that the same serialized tab objects the earlier fix withheld continue to be served, from the closed-tab history rather than the live layout. Summary Three routes, /api/storage/getLocalStorage, getLocalStorageVal and getLocalStorageVals, are registered with CheckAuth only and are reachable by the publish RoleReader token and anonymously when Publish.Auth.Enable is false. All three call model.GetLocalStorage() and then, for read-only roles,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xp3q-r38w-vgqm

  2. Revision 2 · amended ·

    Amended from ghsa record GHSA-xp3q-r38w-vgqm

  3. Revision 1 · created ·

    Published from osv record GHSA-xp3q-r38w-vgqm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-xp3q-r38w-vgqm

Advisory: SiYuan: The publish filter for local storage returns the administrator's entire storage map with only three keys sanitized
IDs: GHSA-xp3q-r38w-vgqm
Record: https://patchnext.com/advisories/ghsa-xp3q-r38w-vgqm (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260729005258-4daee87d4152. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260729005258-4daee87d4152; fixed in 0.0.0-20260729005258-4daee87d4152

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xp3q-r38w-vgqm (OSV record GHSA-xp3q-r38w-vgqm lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260729005258-4daee87d4152 (fixed))
- Verified: https://github.com/advisories/GHSA-xp3q-r38w-vgqm (GitHub-reviewed advisory GHSA-xp3q-r38w-vgqm lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260729005258-4daee87d4152)

Commands are suggestions: review each one before running it.

Loading voting…