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

Exploitation

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

CVSS

6.6 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L

EPSS

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

Summary 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-enabled plugin as packageName while pointing repoURL/ repoHash at different, attacker-influenced content, silently overwriting the existing plugin's files. Affected code kernel/api/bazaar.go: kernel/model/bazaar.go: kernel/bazaar/install.go: installPath is derived solely from packageName; the downloaded data is derived solely from repoURL/repoHash; nothing cross-validates them, and installPackage performs no check for whether installPath already contains an existing package before copying into it. The same pattern applies to the widget/icon/template/theme install endpoints, which share…

Published by the source

23 Oct 2026, 18:38 UTC

Last modified by the source

23 Oct 2026, 18:45 UTC

Source last checked

26 Oct 2026, 15:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rpx2-p6hp-x5gj

2. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rpx2-p6hp-x5gj

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rpx2-p6hp-x5gj

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

# Patch Next advisory brief: CVE-2026-62204

Advisory: SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin
IDs: CVE-2026-62204, GHSA-rpx2-p6hp-x5gj
Record: https://patchnext.com/advisories/cve-2026-62204 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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-20260808010544-26ccb40d390e. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260808010544-26ccb40d390e; fixed in 0.0.0-20260808010544-26ccb40d390e

## 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-rpx2-p6hp-x5gj (OSV record GHSA-rpx2-p6hp-x5gj lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260808010544-26ccb40d390e (fixed))
- Verified: https://github.com/advisories/GHSA-rpx2-p6hp-x5gj (GitHub-reviewed advisory GHSA-rpx2-p6hp-x5gj lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260808010544-26ccb40d390e)

Commands are suggestions: review each one before running it.