Skip to content

← Actionable
High, CVSS 7.5amended

SiYuan: Encrypted-notebook key-derivation material and wrapped notebook keys disclosed to anonymous readers, enabling offline master-password cracking

CVE-2026-72801GHSA-8x84-r2ff-h8pq

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-20260724102025-3bc014c7dc32), 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
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-72801: 0.30% estimated exploitation activity in the next 30 days; percentile 23.38 (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-72801. Summary Two CheckAuth-only endpoints disclose the complete offline attack material for the encrypted-notebook master password, plus the wrapped per-notebook key needed to use it. Both are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. An unauthenticated remote client can retrieve the Argon2id salt and cost parameters, a verifier that confirms a correct password offline, and the encrypted per-notebook data key reducing the security of every encrypted notebook to the master password's resistance to offline GPU cracking. Details (1) POST /api/system/getConf leaks NotebookCrypto. getConf → GetMaskedConf() marshals the full configuration including NotebookCrypto conf.NotebookCrypto (JSON tag notebookCrypto, not -, so it survives the deep copy). For non-administrators HideConfSecret() is applied, which nulls a dozen secret-bearing fields like AI, MCPOAuth, Api, Flashcard,…

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

    Amended from ghsa record GHSA-8x84-r2ff-h8pq

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6392

  3. Revision 1 · created ·

    Published from osv record GHSA-8x84-r2ff-h8pq

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-72801

Advisory: SiYuan: Encrypted-notebook key-derivation material and wrapped notebook keys disclosed to anonymous readers, enabling offline master-password cracking
IDs: CVE-2026-72801, GHSA-8x84-r2ff-h8pq
Record: https://patchnext.com/advisories/cve-2026-72801 (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: High (CVSS 7.5)
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-20260724102025-3bc014c7dc32. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260724102025-3bc014c7dc32; fixed in 0.0.0-20260724102025-3bc014c7dc32

## 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-8x84-r2ff-h8pq (OSV record GHSA-8x84-r2ff-h8pq lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724102025-3bc014c7dc32 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6392 (OSV record GO-2026-6392 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724102025-3bc014c7dc32 (fixed))
- Verified: https://github.com/advisories/GHSA-8x84-r2ff-h8pq (GitHub-reviewed advisory GHSA-8x84-r2ff-h8pq lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724102025-3bc014c7dc32)

Commands are suggestions: review each one before running it.

Loading voting…