SiYuan: /history/*path and /repo/diff/*path potentially exposing historical snapshots of data/.siyuan/publishAccess.json and data/templates/*

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-82651: 0.48% estimated exploitation activity in the next 30 days; percentile 41.27 (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 GHSA-c8r8-95hg-mp34 added a centralized guard, util.IsForbiddenAbsPath(), specifically to block access to a small set of sensitive files: conf/conf.json (plaintext accessAuthCode/API token/cookie key), data/snippets/conf.json, the entire data/templates/ directory, and data/.siyuan/publishAccess.json (plaintext publish-mode passwords). It was applied to kernel/api/file.go and kernel/mcp/tools/file.go. Two other routes in the same server that serve arbitrary files by path, /history/path and /repo/diff/path, construct their target paths independently and were not updated to call this new guard. Since the repo/history snapshot system's tracked root is data/ (confirmed by getSyncIgnoreLines(), whose ignore file lives at data/.siyuan/syncignore with entries relative to data/), both data/.siyuan/publishAccess.json and data/templates/ fall within the scope that can legitimately be captured in historical snapshots, meaning a prior version of either file can exist in…

Published by the source

5 Oct 2026, 17:32 UTC

Last modified by the source

7 Oct 2026, 17:55 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3cm4-ccvw-6xr6

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6662

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3cm4-ccvw-6xr6

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

# Patch Next advisory brief: CVE-2026-82651

Advisory: SiYuan: /history/*path and /repo/diff/*path potentially exposing historical snapshots of data/.siyuan/publishAccess.json and data/templates/*
IDs: CVE-2026-82651, GHSA-3cm4-ccvw-6xr6
Record: https://patchnext.com/advisories/cve-2026-82651 (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 4.9)
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-20260816034002-035bf9a8c311. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260816034002-035bf9a8c311; fixed in 0.0.0-20260816034002-035bf9a8c311

## 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-6662 (OSV record GO-2026-6662 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260816034002-035bf9a8c311 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-3cm4-ccvw-6xr6 (OSV record GHSA-3cm4-ccvw-6xr6 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260816034002-035bf9a8c311 (fixed))
- Verified: https://github.com/advisories/GHSA-3cm4-ccvw-6xr6 (GitHub-reviewed advisory GHSA-3cm4-ccvw-6xr6 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260816034002-035bf9a8c311)

Commands are suggestions: review each one before running it.