CVE-2026-58487 hedgedoc CVE debrief

Who should care

Users of HedgeDoc versions prior to 1.11.0 should apply the patch to prevent stored HTML injection attacks. Operators of HedgeDoc instances should review user email addresses to prevent similar vulnerabilities. Security teams should monitor for suspicious activity on the HedgeDoc application. Platform administrators should ensure that the patch is applied to all affected systems.

Technical summary

HedgeDoc accepted RFC 5321 quoted-string local-parts in email addresses during registration. The local-part was then reused as the user's display name without escaping and rendered into HTML in multiple places, including publish and slide views as well as the collaborative editor. An attacker could break out of an HTML attribute and inject arbitrary markup into the page. The deployed Content-Security-Policy prevented straightforward inline JavaScript execution, but the injected HTML was still sufficient to alter page content and embed attacker-controlled resources such as cross-origin iframes.

Defensive priority

Medium

Recommended defensive actions

• Apply the patch to upgrade to HedgeDoc version 1.11.0 or later
• Review and update user email addresses to prevent similar vulnerabilities
• Monitor for suspicious activity on the HedgeDoc application
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-13T22:16:48.410Z and has not been modified since then. The NVD entry is currently 5.1 MEDIUM. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability affects HedgeDoc versions prior to 1.11.0.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.