Quick answers
- Is CVE-2026-58486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58486 being exploited in the wild.
- How severe is CVE-2026-58486?
- Informational severity, with a CVSS score of 8.3, published 13 July 2026.
- Which products and versions are affected?
- HedgeDoc < 1.11.0.
- Is there a fix for CVE-2026-58486?
- A patch was published on 2026-06-18: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58486 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58486?
- Check whether you run HedgeDoc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
HedgeDoc prior to version 1.11.0 used an insecure YAML parser (js-yaml v3 via @hedgedoc/meta-marked) that resolved YAML anchor aliases by default. An attacker with note-creation privileges can submit a compact YAML payload in the note frontmatter that expands into a massive object structure upon parsing. This expansion occurs on every request to the publish (/s/<shortid>) or editor (/<noteId>) views, saturating the single-threaded Node.js event loop for several minutes per request. Because the malicious payload is stored in the database, the DoS effect persists across application restarts. The issue was resolved in version 1.11.0 by switching to js-yaml v4 and implementing constraints on object depth and string length.
Affected products
- HedgeDoc HedgeDoc < 1.11.0
Timeline
- 2026-06-18: advisory: GitHub Security Advisory published
- 2026-06-18: patched: Fix committed to repository
- 2026-07-13: disclosed: CVE published to NVD