{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58486 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58486 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58486 is a high-severity denial of service vulnerability in hedgedoc, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58486 and fix it if it is affected.\n\nWhat it is: CVE-2026-58486 is a high-severity denial of service vulnerability in hedgedoc, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-58486 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-58486/ (Markdown: https://insights.sbomify.com/CVE-2026-58486/index.md)","id":"CVE-2026-58486","markdown":"https://insights.sbomify.com/CVE-2026-58486/index.md","name":"CVE-2026-58486","record":{"aliases":["GHSA-qj78-mjch-wwrv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HedgeDoc notes application","requires_auth":"low_privilege","summary":"Attackers can cause denial of service in HedgeDoc by submitting malicious YAML frontmatter that exhausts CPU resources via alias expansion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H","version":"4.0"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to version 1.11.0, HedgeDoc was vulnerable to a YAML alias bomb due to unsafe processing of the note frontmatter. HedgeDoc parsed frontmatter with js-yaml.load (js-yaml v3) via @hedgedoc/meta-marked, which resolved YAML anchor aliases. A compact malicious payload could therefore expand into a huge object structure, consuming excessive CPU. This expansion ran on every request to the publish view (/s/\u003cshortid\u003e) and, when placed under the opengraph key, the editor view (/\u003cnoteId\u003e). A ten-level alias bomb could block the single Node.js event loop for roughly 235 seconds per request, causing concurrent requests to hang or drop and rendering the instance unavailable (DoS). Because the note was stored in the database, the impact survived process restarts until the note was removed. toobusy-js did not reliably mitigate the worst cases, as the event loop was saturated before the middleware could respond. This issue was 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: Denial-of-service via YAML alias expansion in note frontmatter","id":"CVE-2026-58486","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"HedgeDoc: Stored HTML injection via email local-part","id":"CVE-2026-58487"},"packages":[],"prev":{"headline":"mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`","id":"CVE-2026-58485"},"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 cause denial of service in HedgeDoc by submitting malicious YAML frontmatter that exhausts CPU resources via alias expansion.","url":"https://insights.sbomify.com/CVE-2026-58486/"}