SiYuan: Non-administrator responses from /api/system/getConf omit three secrets that the configuration-export path explicitly strips, disclosing the session-cookie signing key and the OS username to…

Exploitation

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

CVSS

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

EPSS

• CVE-2026-72793: 0.30% estimated exploitation activity in the next 30 days; percentile 23.35 (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.

CVE: This vulnerability corresponds to CVE-2026-72793. Summary /api/system/getConf is registered with CheckAuth only and is reachable by the publish RoleReader token, and anonymously when Publish.Auth.Enable is false. Its non-administrator masking chain is a blocklist that enumerates fields individually. Three fields that the configuration-export endpoint in the same file deliberately clears are absent from that blocklist and are returned to readers: | Field | JSON | What it is | Cleared by exportConf at | |---|---|---|---| | Conf.CookieKey | cookieKey | The session-cookie signing key | kernel/api/system.go:360 | | Conf.Export.PandocBin | export.pandocBin | Absolute path embedding the OS username | kernel/api/system.go:338 | | Conf.NotebookCrypto | notebookCrypto | Encrypted-notebook key material | kernel/api/system.go:360 | The project has already classified all three as values that must not leave the server. The reader-facing path returns them. Details Route.…

Published by the source

4 Sep 2026, 21:16 UTC

Last modified by the source

10 Sep 2026, 15:15 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-h4v5-crx2-3cv4

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6424

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-h4v5-crx2-3cv4

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

# Patch Next advisory brief: CVE-2026-72793

Advisory: SiYuan: Non-administrator responses from /api/system/getConf omit three secrets that the configuration-export path explicitly strips, disclosing the session-cookie signing key and the OS username to…
IDs: CVE-2026-72793, GHSA-h4v5-crx2-3cv4
Record: https://patchnext.com/advisories/cve-2026-72793 (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 8.6)
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-20260725132049-2d8b98395a91. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260725132049-2d8b98395a91; fixed in 0.0.0-20260725132049-2d8b98395a91

## 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-h4v5-crx2-3cv4 (OSV record GHSA-h4v5-crx2-3cv4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260725132049-2d8b98395a91 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6424 (OSV record GO-2026-6424 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260725132049-2d8b98395a91 (fixed))
- Verified: https://github.com/advisories/GHSA-h4v5-crx2-3cv4 (GitHub-reviewed advisory GHSA-h4v5-crx2-3cv4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260725132049-2d8b98395a91)

Commands are suggestions: review each one before running it.