Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

SiYuan Vulnerable to Remote Code Execution via Malicious Bazaar Package — Marketplace XSS

CVE-2026-56395GHSA-v3mg-9v85-fcm7

What to do

Vendor fix available. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/siyuan-note/siyuan/kernel

    Affected
    <= 0.0.0-20260313024916-fd6526133bb3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source
EPSS
  • CVE-2026-56397: 0.50% estimated exploitation activity in the next 30 days; percentile 42.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Remote Code Execution via Malicious Bazaar Package — Marketplace XSS Summary SiYuan's Bazaar (community marketplace) renders plugin/theme/template metadata and README content without sanitization. A malicious package author can achieve RCE on any user who browses the Bazaar by: 1. Package metadata XSS (zero-click): Package displayName and description fields are injected directly into HTML via template literals without escaping. Just loading the Bazaar page triggers execution. 2. README XSS (one-click): The renderREADME function uses lute.New() without SetSanitize(true), so raw HTML in the README passes through to innerHTML unsanitized. Both vectors execute in Electron's renderer with nodeIntegration: true and contextIsolation: false, giving full OS command execution. Affected Component - Metadata rendering: app/src/config/bazaar.ts:275-277 - README rendering (backend): kernel/bazaar/package.go:635-645 (renderREADME) - README rendering (frontend): app/src/config/bazaar.ts:607…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-v3mg-9v85-fcm7

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GO-2026-4720

Agent brief

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

# Patch Next advisory brief: CVE-2026-56395

Advisory: SiYuan Vulnerable to Remote Code Execution via Malicious Bazaar Package — Marketplace XSS
IDs: CVE-2026-56395, GHSA-v3mg-9v85-fcm7
Record: https://patchnext.com/advisories/cve-2026-56395 (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: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected <= 0.0.0-20260313024916-fd6526133bb3

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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/GO-2026-4720 (OSV record GO-2026-4720 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260317012524-fe4523fff2c8 (fixed))
- Verified: https://github.com/advisories/GHSA-v3mg-9v85-fcm7 (GitHub-reviewed advisory GHSA-v3mg-9v85-fcm7 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <=0.0.0-20260313024916-fd6526133bb3)

Commands are suggestions: review each one before running it.

Loading voting…