SiYuan: Tag labels from password-protected documents are returned to readers who have not entered the password
CVE-2026-72792GHSA-mp7r-57w4-5qm3
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-20260726002639-4515fa257cfa), 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
Go github.com/siyuan-note/siyuan/kernel
- Affected
- < 0.0.0-20260726002639-4515fa257cfa
- Fixed in
- 0.0.0-20260726002639-4515fa257cfa
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-mp7r-57w4-5qm3 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6427 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mp7r-57w4-5qm3 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
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-72792: 0.33% estimated exploitation activity in the next 30 days; percentile 25.60 (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.
CVE: This vulnerability corresponds to CVE-2026-72792. Summary /api/tag/getTag filters its results for reader roles through FilterTagsByPublishIgnore, which checks only the visible publish tier. Documents that are published but password-protected pass that check, so a reader who has never entered a document's publish password receives every tag label used inside it, together with occurrence counts. The project has already treated this exact tier mismatch as a vulnerability on a sibling path: commit 82e9ded42 ("Enforce publish access for graph nodes") moved the graph endpoint off the visible-only filter and onto a password-aware one. FilterTagsByPublishIgnore was not upgraded alongside it. Details | Item | Detail | |---|---| | Route | kernel/api/router.go:194 POST /api/tag/getTag → model.CheckAuth → getTag | | Middleware | CheckAuth only: no CheckReadonly, no CheckAdminRole | | Guard | Present but at the wrong tier: visible-only, no password check | | Exposed | Every tag label…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-mp7r-57w4-5qm3
- Revision 2 · amended ·
Amended from osv record GO-2026-6427
- Revision 1 · created ·
Published from osv record GHSA-mp7r-57w4-5qm3
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-72792 Advisory: SiYuan: Tag labels from password-protected documents are returned to readers who have not entered the password IDs: CVE-2026-72792, GHSA-mp7r-57w4-5qm3 Record: https://patchnext.com/advisories/cve-2026-72792 (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-20260726002639-4515fa257cfa. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260726002639-4515fa257cfa; fixed in 0.0.0-20260726002639-4515fa257cfa ## 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-mp7r-57w4-5qm3 (OSV record GHSA-mp7r-57w4-5qm3 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6427 (OSV record GO-2026-6427 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa (fixed)) - Verified: https://github.com/advisories/GHSA-mp7r-57w4-5qm3 (GitHub-reviewed advisory GHSA-mp7r-57w4-5qm3 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726002639-4515fa257cfa) Commands are suggestions: review each one before running it.
Loading voting…