cve.bz

CVE-2026-62204 siyuan-note siyuan

5.9 mediumEPSS 0.09%Fix available

Medium (5.9) in siyuan-note siyuan. EPSS 0.09% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/siyuan-note/siyuan/kernel 0.0.0-20260808010544-26ccb40d390e.

On this page
SiYuan versions before v3.7.4 fail to validate that packageName matches the downloaded package content in bazaar install endpoints. Attackers with same-origin access can overwrite existing trusted plugins by supplying mismatched packageName and repoURL parameters, achieving persistence across application restarts.

Severity

CVSS 4.0

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

CVSS 3.1

6.6 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L
EPSS
0.09% (unchanged from 0.09% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st 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-26. 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-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity Failures
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-62204 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62204?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62204?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-62204 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.7.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rpx2-p6hp-x5gjGogithub.com/siyuan-note/siyuan/kernel<0.0.0-20260808010544-26ccb40d390e0.0.0-20260808010544-26ccb40d390e
GO-2026-6834Gogithub.com/siyuan-note/siyuan/kernel<0.0.0-20260808010544-26ccb40d390e0.0.0-20260808010544-26ccb40d390e

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.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON