{"answers":{"affected":"2 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.","exploited":"There is no known exploitation of CVE-2026-73630 in the wild and no public exploit code.","fix":"Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260731093152-c7522b8db586 or later.","what":"CVE-2026-73630 is a medium-severity vulnerability in siyuan-note siyuan, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73630 and fix it if it is affected.\n\nWhat it is: CVE-2026-73630 is a medium-severity vulnerability in siyuan-note siyuan, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73630 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260731093152-c7522b8db586\n- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260731093152-c7522b8db586\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-73630/ (Markdown: https://insights.sbomify.com/CVE-2026-73630/index.md)","id":"CVE-2026-73630","markdown":"https://insights.sbomify.com/CVE-2026-73630/index.md","name":"CVE-2026-73630","record":{"aliases":["GHSA-4pjg-x8qj-33j5"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SiYuan note-taking app","requires_auth":"none","summary":"An anonymous attacker can confirm the existence of hidden or forbidden documents and obtain publish-auth cookies for them via the authFilePublishAccess endpoint.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"SiYuan before v3.7.4 contains an information disclosure vulnerability in the /api/filetree/authFilePublishAccess endpoint, which is registered with CheckAuth only and is reachable anonymously. The endpoint never sets a failure code, so its outcome is signalled entirely by the response message and by the presence of a Set-Cookie header, and these signals differ across access tiers. By submitting requests with an empty password for a candidate document identifier, an anonymous attacker can distinguish whether a document is public/nonexistent, password-protected, or exists at the hidden or forbidden tier, thereby confirming the existence of documents they are not permitted to access. Because hidden and forbidden entries store an empty password, such requests also cause the server to issue a publish-auth cookie for forbidden documents.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SiYuan before v3.7.4 Information Disclosure via authFilePublishAccess","id":"CVE-2026-73630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Apache Struts: Shared parsing state in the JSON plugin","id":"CVE-2026-73631"},"packages":[{"ecosystem":"Go","fixed":["0.0.0-20260731093152-c7522b8db586"],"introduced":["0"],"last_affected":[],"package":"github.com/siyuan-note/siyuan/kernel","purl":null,"source":"GHSA-4pjg-x8qj-33j5"},{"ecosystem":"Go","fixed":["0.0.0-20260731093152-c7522b8db586"],"introduced":["0"],"last_affected":[],"package":"github.com/siyuan-note/siyuan/kernel","purl":"pkg:golang/github.com/siyuan-note/siyuan/kernel","source":"GHSA-4pjg-x8qj-33j5"}],"prev":{"headline":"Serendipity before 2.6.0 SSRF via hex IPv4 and IPv6 addresses","id":"CVE-2026-73629"},"products":["siyuan"],"published":"2026-08-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["siyuan-note"]},"summary":"An anonymous attacker can confirm the existence of hidden or forbidden documents and obtain publish-auth cookies for them via the authFilePublishAccess endpoint.","url":"https://insights.sbomify.com/CVE-2026-73630/"}