{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41421 exists.","fix":"No fix has been published for CVE-2026-41421 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41421 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41421 and fix it if it is affected.\n\nWhat it is: CVE-2026-41421 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41421 exists.\n\nAffected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41421/ (Markdown: https://insights.sbomify.com/CVE-2026-41421/index.md)","id":"CVE-2026-41421","markdown":"https://insights.sbomify.com/CVE-2026-41421/index.md","name":"CVE-2026-41421","record":{"aliases":["GHSA-grjj-6f6g-cq8q"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SiYuan knowledge management","requires_auth":"low_privilege","summary":"Attacker can execute arbitrary code on desktop via XSS in notifications due to insecure Electron configuration.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SiYuan Desktop Notification XSS Leads to Electron RCE","id":"CVE-2026-41421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Daptin vulnerable to SQL injection via unvalidated goqu.L() calls in aggregate API","id":"CVE-2026-41422"},"packages":[],"prev":{"headline":"4ga Boards: Import Path Traversal Leads to Arbitrary File Read","id":"CVE-2026-41419"},"products":["siyuan"],"published":"2026-04-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-25","vendors":["siyuan-note"]},"summary":"Attacker can execute arbitrary code on desktop via XSS in notifications due to insecure Electron configuration.","url":"https://insights.sbomify.com/CVE-2026-41421/"}