Skip to content

← Actionable
Medium, CVSS 5.8amended

SiYuan discloses an administrator's open documents and search terms to anonymous readers

CVE-2026-72788GHSA-hgfg-j9pg-43xw

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-20260812083335-251596fc0de2), 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
  • CVE-2026-72788: 0.38% estimated exploitation activity in the next 30 days; percentile 31.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary /api/system/getConf serves Conf.UILayout to publish readers after passing it through FilterConfByPublishIgnore, whose only function is to filter that layout. The layout is written exclusively by setUILayout, which is administrator-gated, so what readers receive is the administrator's own live workspace state, re-saved on every tab open, close and focus change. The filter that is supposed to protect it, filterLayoutItemByPublishIgnore, has four separate defects. Together they mean a single unauthenticated POST with no arguments returns the titles and identifiers of the administrator's open password-protected documents, the titles of documents in locked or closed notebooks, their recent search terms and the paths those searches were scoped to, and the paths of private assets they have open. This report concerns FilterConfByPublishIgnore and its layout walker. It is distinct from the previously reported getConf issues, which concern configuration fields surviving…

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

    Amended from ghsa record GHSA-hgfg-j9pg-43xw

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6622

  3. Revision 1 · created ·

    Published from osv record GHSA-hgfg-j9pg-43xw

Agent brief

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

# Patch Next advisory brief: CVE-2026-72788

Advisory: SiYuan discloses an administrator's open documents and search terms to anonymous readers
IDs: CVE-2026-72788, GHSA-hgfg-j9pg-43xw
Record: https://patchnext.com/advisories/cve-2026-72788 (revision 3, source checked 26 Oct 2026, 15:29 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-20260812083335-251596fc0de2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260812083335-251596fc0de2; fixed in 0.0.0-20260812083335-251596fc0de2

## 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/GO-2026-6622 (OSV record GO-2026-6622 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-hgfg-j9pg-43xw (OSV record GHSA-hgfg-j9pg-43xw lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://github.com/advisories/GHSA-hgfg-j9pg-43xw (GitHub-reviewed advisory GHSA-hgfg-j9pg-43xw lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2)

Commands are suggestions: review each one before running it.

Loading voting…