{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58489 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58489 is a medium-severity vulnerability in hedgedoc, published on 13 Jul 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-58489 and fix it if it is affected.\n\nWhat it is: CVE-2026-58489 is a medium-severity vulnerability in hedgedoc, published on 13 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-58489 in the wild and no public exploit code.\n\nAffected product: hedgedoc. 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-58489/ (Markdown: https://insights.sbomify.com/CVE-2026-58489/index.md)","id":"CVE-2026-58489","markdown":"https://insights.sbomify.com/CVE-2026-58489/index.md","name":"CVE-2026-58489","record":{"aliases":["GHSA-8v9p-5j95-826j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"HedgeDoc markdown notes","requires_auth":"low_privilege","summary":"Attackers can trick logged-in users into exporting private notes to attacker-controlled GitHub Gists via a CSRF vulnerability in the OAuth callback.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.0, the GitHub Gist export flow created an OAuth2  state  value but only checked that it was present rather than validating it against the value expected for the user's session. Because the state was not properly validated, an attacker could forge a callback URL containing their own valid GitHub OAuth code. When processing the callback, HedgeDoc used the victim's logged-in session to select which note to export, but the attacker's authorization code to determine which GitHub account received it. As a result, a logged-in victim who clicked a crafted link could export their own private, protected, or limited note directly into a Gist controlled by the attacker. This issue has been fixed in version 1.11.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"HedgeDoc: CSRF in GitHub Gist export callback","id":"CVE-2026-58489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Warpgate: Reflected XSS in SSO return endpoint via attacker-controlled next parameter","id":"CVE-2026-58491"},"packages":[],"prev":{"headline":"HedgeDoc: Rate-limit bypass via CF-Connecting-IP header spoofing","id":"CVE-2026-58488"},"products":["hedgedoc"],"published":"2026-07-13","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["hedgedoc"]},"summary":"Attackers can trick logged-in users into exporting private notes to attacker-controlled GitHub Gists via a CSRF vulnerability in the OAuth callback.","url":"https://insights.sbomify.com/CVE-2026-58489/"}