dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-56395

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SiYuan before v3.6.1 fails to sanitize package metadata and README content in the Bazaar marketplace, allowing malicious package authors to inject arbitrary HTML and JavaScript. Attackers can achieve remote code execution on any user browsing the Bazaar by embedding XSS payloads in package displayName, description, or README fields, exploiting Electron's nodeIntegration setting to execute OS commands.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SiYuan's Bazaar marketplace fails to sanitize package metadata (displayName, description) and README content before rendering, allowing malicious package authors to inject arbitrary HTML/JavaScript. Because SiYuan runs as an Electron app with nodeIntegration enabled, this XSS vulnerability escalates to remote code execution on any user browsing the affected package.

MitigationUpgrade to SiYuan v3.6.1 or later which sanitizes package metadata. Additionally, disable nodeIntegration and enable contextIsolation in Electron to prevent XSS-to-RCE chains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SiYuan installed version
    Open SiYuan and navigate to Help > About, or check the executable file properties. Alternatively, look for a config file containing version info in the application data directory (typically ~/.config/siyuan/ on Linux, %APPDATA%\siyuan\ on Windows, or ~/Library/Application Support/siyuan/ on macOS).
    Affected if The installed version is earlier than v3.6.1 (e.g., v3.6.0, v3.5.x, or any earlier release).
  2. Verify Electron nodeIntegration setting
    Locate the Electron configuration file within the SiYuan application data directory or the application resources. Look for a main.js, config.json, or similar file that contains Electron webPreferences settings. Search for the nodeIntegration parameter.
    Affected if nodeIntegration is set to true or enabled without proper sandboxing configuration.
  3. Inspect Bazaar marketplace package metadata
    Navigate to the Bazaar marketplace within SiYuan (Settings > Bazaar). Review installed packages. Check each package's displayName, description fields, and any embedded README content for unexpected HTML tags, script elements, or suspicious URL patterns.
    Affected if Any installed package contains unsanitized HTML (<script>, <iframe>, javascript: URLs) or JavaScript code in its metadata or README that was not intentionally added by the user.

You are affected if running SiYuan versions earlier than v3.6.1 with nodeIntegration enabled and any Bazaar package contains malicious injected metadata or README content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SiYuan v3.6.1 or later which sanitizes package metadata. Additionally, disable nodeIntegration and enable contextIsolation in Electron to prevent XSS-to-RCE chains.

Recommended fix High confidence

SiYuan v3.6.1

  1. Backup your SiYuan data and configuration before upgrading
  2. Download SiYuan v3.6.1 from the official GitHub repository (github.com/siyuan-note/siyuan)
  3. Verify the integrity of the downloaded package using provided checksums
  4. Install v3.6.1 by replacing the existing installation
  5. After upgrade, verify that the Bazaar marketplace loads correctly
  6. Test that package metadata (displayName, description, README) renders safely without executing arbitrary JavaScript
Caveat Review plugin compatibility; major Electron upgrades may affect third-party plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56395 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data