SiYuan: authFilePublishAccess distinguishes hidden and forbidden documents from public and nonexistent ones, and issues a publish-auth cookie for documents it reports as forbidden

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-73630: 0.34% estimated exploitation activity in the next 30 days; percentile 27.87 (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/filetree/authFilePublishAccess is registered with CheckAuth only and is reachable anonymously. It never sets a failure code, so its outcome is signalled entirely by the response message and by whether a Set-Cookie header is present. Those two signals differ across access tiers, which lets an anonymous caller determine, for any candidate document identifier, whether that document is public or nonexistent, password-protected, or exists at the hidden or forbidden tier. Separately, hidden and forbidden entries carry an empty password. Submitting password:"" therefore satisfies the equality check for them, and the server responds by issuing Set-Cookie: publish-auth-<docID for a document whose own tier is forbidden. Details Route, identical on both refs: No CheckAdminRole, no CheckReadonly. Handler, kernel/api/filetree.go:1608 on the development branch and :1421 on master. ret.Code is never assigned on the failure path, so every response carries code:0. The branch is: The…

Published by the source

23 Oct 2026, 18:31 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-4pjg-x8qj-33j5

2. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4pjg-x8qj-33j5

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4pjg-x8qj-33j5

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

# Patch Next advisory brief: CVE-2026-73630

Advisory: SiYuan: authFilePublishAccess distinguishes hidden and forbidden documents from public and nonexistent ones, and issues a publish-auth cookie for documents it reports as forbidden
IDs: CVE-2026-73630, GHSA-4pjg-x8qj-33j5
Record: https://patchnext.com/advisories/cve-2026-73630 (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-20260731093152-c7522b8db586. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260731093152-c7522b8db586; fixed in 0.0.0-20260731093152-c7522b8db586

## 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-4pjg-x8qj-33j5 (OSV record GHSA-4pjg-x8qj-33j5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260731093152-c7522b8db586 (fixed))
- Verified: https://github.com/advisories/GHSA-4pjg-x8qj-33j5 (GitHub-reviewed advisory GHSA-4pjg-x8qj-33j5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260731093152-c7522b8db586)

Commands are suggestions: review each one before running it.