{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100641 exists.","fix":"No fix has been published for CVE-2026-100641 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100641 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-100641 and fix it if it is affected.\n\nWhat it is: CVE-2026-100641 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100641 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-100641/ (Markdown: https://insights.sbomify.com/CVE-2026-100641/index.md)","id":"CVE-2026-100641","markdown":"https://insights.sbomify.com/CVE-2026-100641/index.md","name":"CVE-2026-100641","record":{"aliases":["GHSA-2mmf-4xwm-55rm","GHSA-wvmc-29rv-83j2"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SiYuan note-taking app","requires_auth":"low_privilege","summary":"Stored XSS in SiYuan allows attackers to execute arbitrary code on the host via malicious flashcard content processed by the privileged Electron renderer.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"SiYuan before v3.8.4 does not HTML-escape stored flashcard block content before interpolating it into the card-manager list markup. Block content returned by /api/riff/getRiffCards is inserted into a card item template in app/src/card/viewCards.ts and assigned to listElement.innerHTML, so content such as \u003cimg src=invalid onerror=...\u003e becomes an executable event-handler attribute. Because the SiYuan desktop (Electron) main window is created with nodeIntegration enabled and contextIsolation disabled, an administrator who opens the card manager on a workspace containing attacker-supplied flashcard content (for example introduced through contribution or import) executes the attacker's script in a privileged renderer, which can lead to arbitrary code execution on the host. The affected endpoint remains behind authentication and administrator-role checks; this is an untrusted-content-to-privileged-renderer issue, not an authorization bypass.","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 before v3.8.4 Stored XSS via Unescaped Flashcard Content","id":"CVE-2026-100641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"SiYuan v2.1.0 before v3.8.4 Cross-Site Request Forgery via CheckAuth","id":"CVE-2026-100642"},"packages":[],"prev":{"headline":"SiYuan before v3.8.4 Clipboard Data Disclosure via IPC","id":"CVE-2026-100640"},"products":["siyuan"],"published":"2026-09-26","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-10-05","vendors":["siyuan-note"]},"summary":"Stored XSS in SiYuan allows attackers to execute arbitrary code on the host via malicious flashcard content processed by the privileged Electron renderer.","url":"https://insights.sbomify.com/CVE-2026-100641/"}