{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75917 exists.","fix":"No fix has been published for CVE-2026-75917 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75917 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 19 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-75917 and fix it if it is affected.\n\nWhat it is: CVE-2026-75917 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 19 Aug 2026. It can only be exploited from the same machine or local 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-75917 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-75917/ (Markdown: https://insights.sbomify.com/CVE-2026-75917/index.md)","id":"CVE-2026-75917","markdown":"https://insights.sbomify.com/CVE-2026-75917/index.md","name":"CVE-2026-75917","record":{"aliases":["GHSA-w6j4-pg6w-qwj7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SiYuan note-taking app","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands by injecting XSS payloads into document metadata fields, exploiting Electron's insecure configuration in SiYuan.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"SiYuan before v3.7.4 contains a cross-site scripting vulnerability in the file-tree picker's hover-tooltip generation (app/src/util/pathName.ts, getLeaf()/movePathTo()) used by the 'move/link to' path-selection dialogs, where document metadata fields (bookmark, alias, memo, and an alternate name field) are concatenated into the aria-label HTML attribute without escaping. A document crafted with a double quote in any of these fields breaks out of the attribute context and injects arbitrary HTML attributes including inline event handlers (e.g., onmouseover). Because every SiYuan Electron BrowserWindow runs with nodeIntegration:true, contextIsolation:false, and no CSP, the injected handler gains require('child_process') access, escalating the XSS to arbitrary OS command execution when a victim merely hovers over the malicious document entry in the path-picker dialog. Malicious documents reach victims via sharing, sync, or import.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SiYuan before v3.7.4 XSS-to-RCE via pathName.ts","id":"CVE-2026-75917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File","id":"CVE-2026-75918"},"packages":[],"prev":{"headline":"SiYuan XSS-to-RCE via unescaped block metadata in hint popup","id":"CVE-2026-75916"},"products":["siyuan"],"published":"2026-08-19","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-08","vendors":["siyuan-note"]},"summary":"Attackers can execute arbitrary OS commands by injecting XSS payloads into document metadata fields, exploiting Electron's insecure configuration in SiYuan.","url":"https://insights.sbomify.com/CVE-2026-75917/"}