CVE-2026-58489

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.0, the GitHub Gist export flow created an OAuth2  state  value but only checked that it was present rather than validating it against the value expected for the user's session. Because the state was not properly validated, an attacker could forge a callback URL containing their own valid GitHub OAuth code. When processing the callback, HedgeDoc used the victim's logged-in session to select which note to export, but the attacker's authorization code to determine which GitHub account received it. As a result, a logged-in victim who clicked a crafted link could export their own private, protected, or limited note directly into a Gist controlled by the attacker. This issue has been fixed in version 1.11.0.

CVSS v3
6.8
EG Score
6.8(low)
EPSS
2.7%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

CSRF in GitHub Gist export callback · Advisory · hedgedoc/hedgedoc · GitHub

https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-8v9p-5j95-826j
github_commit Patch Available

commit fbd7307f1627 (hedgedoc/hedgedoc)

Patch available: hedgedoc/hedgedoc 1.11.0 (contains commit fbd7307f1627)

https://github.com/hedgedoc/hedgedoc/commit/fbd7307f162754212046ec343cbe691223a48c8d

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 01:12 UTCEG score recompute
  6. 2026-07-13 22:48 UTCEG score recompute
  7. 2026-07-13 22:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58489?
CVE-2026-58489 is a medium vulnerability published on July 13, 2026. HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.0, the GitHub Gist export flow created an OAuth2 state value but only checked that it was present rather than validating it against the value expected for the user's session. Because the state was not…
When was CVE-2026-58489 disclosed?
CVE-2026-58489 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58489 actively exploited?
CVE-2026-58489 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58489?
CVE-2026-58489 has a CVSS v3 base score of 6.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-58489?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58489, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58489

Explore →

Is Your Infrastructure Affected by CVE-2026-58489?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.