Quick answers
- Is CVE-2026-58489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58489 being exploited in the wild.
- How severe is CVE-2026-58489?
- Informational severity, with a CVSS score of 6.8, published 13 July 2026.
- Which products and versions are affected?
- HedgeDoc < 1.11.0.
- Is there a fix for CVE-2026-58489?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58489 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-58489?
- 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
A Cross-Site Request Forgery (CSRF) vulnerability exists in the GitHub Gist export callback of HedgeDoc versions prior to 1.11.0. The application failed to validate the OAuth2 'state' parameter, only checking for its presence rather than verifying it against the user's session. An attacker can exploit this by generating a valid GitHub OAuth authorization code for their own account and crafting a malicious callback URL. If a logged-in victim visits this URL, the application uses the victim's session to identify the note to be exported but uses the attacker's authorization code to authenticate the destination GitHub account. This results in the victim's private notes being exported to the attacker's Gist. The vulnerability requires GitHub OAuth to be enabled and requires user interaction (clicking a link). It is fixed in version 1.11.0.
Affected products
- HedgeDoc HedgeDoc < 1.11.0
Timeline
- 2026-06-18: advisory: GitHub Security Advisory published by maintainers
- 2026-07-13: disclosed: CVE published to NVD