ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-62204

SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin

Published Aug 22, 2026 · catalog updated Oct 23, 2026 · SiYuan: Missing consistency check

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-62204. A missing EPSS score is not a low risk. Compare SiYuan: Missing consistency check with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SiYuan: Missing consistency check).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium6.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Version ranges on file
Affected products
Go github.com/siyuan-note/siyuan/kernel · go github.com/siyuan-note/siyuan/kernel · golang github.com · vendor siyuan-note siyuan

## Summary (and the equivalent endpoints for widgets/icons/templates/themes) accept , , and as independent request fields with no validation that they refer to the same package. alone determines the install destination; / alone determine what content gets downloaded and written there. A request can name an already-installed, already-enabled plugin as while pointing / at different, attacker-influenced content, silently overwriting the existing plugin's files. ## Affected code : : : is derived solely from ; the downloaded is derived solely from / ; nothing cross-validates them, and performs no check for whether already contains an existing package before copying into it. The same pattern applies to the widget/icon/template/theme install endpoints, which share . This does not involve path traversal — always resolves inside (or the corresponding directory for other package types), so this is not an instance of "arbitrary file write outside the workspace path" (excluded by this project's SECURITY.md). The issue is that the write lands in the *wrong, existing* location within the intended directory, not outside it — an authorization/identity-verification gap, not a path traversal. ## Reachability / why this is not trivially remote The bazaar endpoints are gated by , , . When no lock-screen password is configured (the common desktop default), still enforces a same-origin check: I verified / correctly parse the header via and check exact hostname / loopback IP: This was tested against common bypass patterns (subdomain-suffix tricks like , and as sent by sandboxed iframes) and found no bypass — this is a correctly-implemented check. This means a purely remote attacker (e.g. a malicious website) cannot invoke this endpoint via CSRF; a request must originate from SiYuan's own renderer origin. ## Realistic impact Given SiYuan runs as an Electron app with (per prior advisories in this repository), a same-origin script-execution primitive (e.g. an XSS bug in the renderer, of whic

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/siyuan-note/siyuan/kernel0 → 0.0.0-20260808010544-26ccb40d390e
  • go github.com/siyuan-note/siyuan/kernel< 0.0.0-20260808010544-26ccb40d390e
  • golang github.comversion unspecified
  • vendor siyuan-note siyuanversion unspecified

How to fix CVE-2026-62204

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-62204. A missing EPSS score is not a low risk. Compare SiYuan: Missing consistency check with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 0.0.0-20260808010544-26ccb40d390e, < 0.0.0-20260808010544-26ccb40d390e. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-345: Insufficient Verification of Data Authenticity; CWE-668: Exposure of Resource to Wrong Sphere. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · GitHub Advisory Database

    Detected

    ## Summary (and the equivalent endpoints for widgets/icons/templates/themes) accept , , and as independent request fields with no validation that they refer to the same package. alone determines the install destination; / alone determine what content gets downloaded and written there. A request can name an already-installed, already-enabled plugin as while pointing / at different, attacker-influen

  2. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260808010544-26ccb40d390e

  3. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    github.com/siyuan-note/siyuan/kernel fixed in 0.0.0-20260808010544-26ccb40d390e

  4. Oct 23, 2026 · GitHub Advisory Database

    Updated

    ## Summary (and the equivalent endpoints for widgets/icons/templates/themes) accept , , and as independent request fields with no validation that they refer to the same package. alone determines the install destination; / alone determine what content gets downloaded and written there. A request can name an already-installed, already-enabled plugin as while pointing / at different, attacker-influen

Sources

  • CVE.orgVulnerability recordCVE-2026-62204

    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 persi

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-rpx2-p6hp-x5gj

    SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-62204

    installBazaarPlugin (and the equivalent endpoints for widgets/icons/templates/themes) accept packageName, repoURL, and repoHash as independent request fields with no validation that they refer to the same package. packageName alone determines the install destination; repoURL/repoHash alone determine what content gets downloaded and written there. A request can name an already-installed, already-en

    advisories.gitlab.com
  • Go Vulnerability DatabasePackage advisoryGHSA-rpx2-p6hp-x5gj

    SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-rpx2-p6hp-x5gj

    SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin

    osv.dev

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.