cve.bz

CVE-2026-60083 siyuan-note siyuan: Incorrect Authorization

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in siyuan-note siyuan. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/siyuan-note/siyuan/kernel 0.0.0-20260808051406-3542530c505f.

On this page
SiYuan versions before v3.8.0 contain an incomplete path blocklist in the MCP file tool that fails to restrict access to sensitive workspace files protected by the HTTP API. Authenticated administrators can read plaintext publish-mode passwords from data/.siyuan/publishAccess.json and access other sensitive files like data/templates and data/snippets/conf.json.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-60083 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-60083?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-60083?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-60083 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
siyuan-note siyuanbefore 3.8.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c8r8-95hg-mp34Gogithub.com/siyuan-note/siyuan/kernel<0.0.0-20260808051406-3542530c505f0.0.0-20260808051406-3542530c505f
GO-2026-6863Gogithub.com/siyuan-note/siyuan/kernel<0.0.0-20260808051406-3542530c505f0.0.0-20260808051406-3542530c505f

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE.

References

Check your stackJSON