dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-41421

HIGH · 8.8 CVSS v3.1 Published 2026-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

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 is an open-source personal knowledge management system. Prior to 3.6.5, SiYuan desktop renders notification messages as raw HTML inside an Electron renderer. The notification route POST /api/notification/pushMsg accepts a user-controlled msg value, forwards it through the backend broadcast layer, and the frontend inserts it into the DOM with insertAdjacentHTML(...) at message.ts. On desktop builds, this is not limited to ordinary XSS. Electron windows are created with nodeIntegration: true, contextIsolation: false, and webSecurity: false at main.js. As a result, JavaScript executed from the notification sink can directly access Node APIs and escalate to desktop code execution. This vulnerability is fixed in 3.6.5.

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 desktop versions prior to 3.6.5 render notification messages as raw HTML using insertAdjacentHTML without sanitization, creating an XSS vulnerability. The POST /api/notification/pushMsg endpoint accepts user-controlled msg values that flow through the backend to the frontend. Combined with insecure Electron settings (nodeIntegration: true, contextIsolation: false, webSecurity: false), JavaScript in notifications can access Node APIs and achieve remote code execution.

MitigationUpgrade to SiYuan 3.6.5 or later. If unable to upgrade immediately, implement input validation/sanitization on the notification endpoint and reconfigure Electron to disable nodeIntegration, enable contextIsolation, and enable webSecurity.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Confirm SiYuan desktop installation
    Locate the SiYuan application installation. On Windows, check %APPDATA%/siyuan or C:/Program Files/SiYuan. On Linux, check ~/.config/siyuan or /opt/siyuan. On macOS, check ~/Library/Application Support/siyuan or /Applications/SiYuan.app. Look for the siyuan executable or the application bundle.
    Affected if SiYuan desktop application is present on the system
  2. Identify installed SiYuan version
    Open the application and navigate to Help > About, or check for a version.json file in the installation directory. Compare the version number to 3.6.5.
    Affected if Installed version is any release prior to 3.6.5 (e.g., 3.6.4, 3.6.3, 3.6.0, etc.)
  3. Inspect Electron security settings
    Locate the main.js or electron main configuration file within the SiYuan installation directory. Search for the webPreferences object when creating the BrowserWindow. Verify the values of nodeIntegration, contextIsolation, and webSecurity settings.
    Affected if nodeIntegration is set to true OR contextIsolation is set to false OR webSecurity is set to false
  4. Verify notification API exposure
    Review application logs or network traffic for POST requests to /api/notification/pushMsg. This endpoint accepts a msg parameter that flows to the frontend notification rendering.
    Affected if The /api/notification/pushMsg endpoint is accessible and the application processes msg values without sanitization

A system is affected if SiYuan desktop version is prior to 3.6.5 AND the Electron configuration contains any of the three insecure settings (nodeIntegration:true, contextIsolation:false, webSecurity:false).

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 3.6.5 or later. If unable to upgrade immediately, implement input validation/sanitization on the notification endpoint and reconfigure Electron to disable nodeIntegration, enable contextIsolation, and enable webSecurity.

Recommended fix High confidence

3.6.5

  1. 1. Check current installed version of SiYuan (Help > About in the application menu)
  2. 2. Download SiYuan version 3.6.5 from the official GitHub releases page or the official website
  3. 3. Backup your SiYuan data folder (typically located at ~/SiYuan or in your user data directory)
  4. 4. Close the current SiYuan application completely
  5. 5. Install version 3.6.5 by running the installer for your platform (Windows/macOS/Linux)
  6. 6. After installation, verify the version by checking Help > About to confirm you are on 3.6.5

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41421 — 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-41421 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