SiYuan: The publish filter for database backlinks consults the forbidden list instead of the visibility list, disclosing hidden-tier documents to anonymous readers

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-73049: 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.

As published by the source; long descriptions are shortened.

Summary /api/av/getAttributeViewBacklinks filters its results for reader roles through FilterAttributeViewBacklinksByPublishAccess. That function resolves its ignore list with GetDisablePublishAccess, which covers only the forbidden tier. Documents at the hidden tier are absent from that list, so they pass the check. The result is that an anonymous reader supplying a publicly visible database row receives the database name, row title and document path of rows in hidden documents that reference it. The rest of the function is correct. It takes gin.Context and calls GetPathPasswordByPublishAccess and CheckPublishAuthCookie at all four decision points, so the password-protected and private tiers are properly enforced. The defect is the choice of list, on one line. Details Route, kernel/api/router.go:545 on the development branch and :527 on master: CheckAuth only. No CheckAdminRole, no CheckReadonly. The defect. In FilterAttributeViewBacklinksByPublishAccess…

Published by the source

23 Oct 2026, 18:30 UTC

Last modified by the source

23 Oct 2026, 18:45 UTC

Source last checked

26 Oct 2026, 15:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p4qw-vx5p-g984

2. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p4qw-vx5p-g984

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p4qw-vx5p-g984

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

# Patch Next advisory brief: CVE-2026-73049

Advisory: SiYuan: The publish filter for database backlinks consults the forbidden list instead of the visibility list, disclosing hidden-tier documents to anonymous readers
IDs: CVE-2026-73049, GHSA-p4qw-vx5p-g984
Record: https://patchnext.com/advisories/cve-2026-73049 (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-20260730150429-5b42614311b0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260730150429-5b42614311b0; fixed in 0.0.0-20260730150429-5b42614311b0

## 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-p4qw-vx5p-g984 (OSV record GHSA-p4qw-vx5p-g984 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260730150429-5b42614311b0 (fixed))
- Verified: https://github.com/advisories/GHSA-p4qw-vx5p-g984 (GitHub-reviewed advisory GHSA-p4qw-vx5p-g984 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260730150429-5b42614311b0)

Commands are suggestions: review each one before running it.