CVE-2026-58486

HedgeDoc: Denial-of-service via YAML alias expansion in note frontmatter

Published Jul 13, 2026 CVSS 4.0 · 8.3 High EPSS < 1% KEV · Not listed
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/<shortid>) and, when placed under the opengraph key, the editor view (/<noteId>). 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.

Analysis

AI-generated

Technical impact

A YAML alias bomb exploit occurs when malicious frontmatter in a HedgeDoc note causes the js‑yaml library to expand a large number of anchor aliases, consuming excessive CPU core time and blocking the single Node.js event loop. This denial‑of‑service condition can keep the publish endpoint (/s/<shortid>) and the editor view (/noteId) unresponsive for approximately 235 seconds per request, allowing concurrent requests to hang or drop and rendering the instance unavailable. The weakness is rooted in uncontrolled resource consumption (CWE‑400) and potential resource exhaustion (CWE‑409).

Affected Systems

Any instance of HedgeDoc running a version earlier than 1.11.0 is vulnerable. The affected product is HedgeDoc, maintained by Hedgedoc. Users of pre‑1.11.0 releases should verify the version and consider upgrade before patching.

Risk and Exploitability

The CVSS score of 8.3 indicates a high‑severity denial‑of‑service vulnerability. The EPSS score of <1 % indicates a very low probability of exploitation, and the fact that the vulnerability is not listed in the CISA KEV catalog suggests that exploit evidence is limited at the time of analysis. Based on the description, it is inferred that an attacker could trigger the DoS by creating or accessing a note with malicious frontmatter on any publicly accessible instance. The likely attack vector is normal HTTP requests to the publish or editor endpoints. An attacker can cause the event loop to be saturated, leading to concurrent requests hanging or dropping and rendering the instance unavailable. The impact persists across service restarts until the offending note is deleted.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HedgeDoc to version 1.11.0 or later to apply the fixed safe YAML parsing logic.
  • Locate and delete any notes that contain large YAML alias bombs before they are accessed, or sanitize their frontmatter to remove anchor expansions.
  • If an immediate upgrade is not possible, restrict or disable public note creation and consider applying server‑side input validation or rate‑limiting to reduce the likelihood of resource exhaustion from malicious payloads.

Generated by OpenCVE AI on July 31, 2026 at 11:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Hedgedoc
Hedgedoc hedgedoc
Vendors & Products Hedgedoc
Hedgedoc hedgedoc
Type Values Removed Values Added
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/<shortid>) and, when placed under the opengraph key, the editor view (/<noteId>). 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.
Title HedgeDoc: Denial-of-service via YAML alias expansion in note frontmatter
Weaknesses CWE-400
CWE-409
References
Metrics cvssV4_0

{'score': 8.3, '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'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 14, 2026, 12:48 PM
Reserved
Jun 30, 2026, 8:21 PM
Status
Deferred
Published
Jul 13, 2026, 11:16 PM
Modified
Jul 14, 2026, 4:42 PM