CVE-2026-52798

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. 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: epss, secondary
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.9Exploit: NoneExposed: 0

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

Gogs is an open source self-hosted Git service. Prior to 0.14.3, although .ipynb previews are sanitized on the server side via /-/api/sanitize_ipynb, the inserted content is re-rendered on the client side without sanitization using marked() on elements with the .nb-markdown-cell class. During this process, links containing schemes such as javascript: can be regenerated. As a result, when a victim views an attacker-crafted .ipynb file and clicks the link, arbitrary JavaScript is executed in the Gogs origin, leading to a click-based Stored XSS. This vulnerability is fixed in 0.14.3.

CVSS v3
8.9
EG Score
8.9(medium)
EPSS
34.6%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Stored XSS in `.ipynb` Preview · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-jq8v-rmf6-65jw
github_release Patch Available

0.14.3

Patch available: gogs/gogs v0.14.3

https://github.com/gogs/gogs/releases/tag/v0.14.3
github_pr

security: upgrade marked.js to 4.3.0

Fix merged in gogs/gogs PR #8319 on 2026-06-04 — awaiting tagged release

https://github.com/gogs/gogs/pull/8319
github_commit

commit 17b168b11ca7 (gogs/gogs)

Fix landed in gogs/gogs commit 17b168b11ca7 — awaiting tagged release

https://github.com/gogs/gogs/commit/17b168b11ca759a7550e1f4bbd68bbde14db7785

Vendor Advisories for CVE-2026-52798(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
gogs.io/gogs0.14.3

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 43× 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-07 04:02 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 15:40 UTCEG score recompute
  5. 2026-07-06 03:32 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 15:18 UTCEG score recompute
  8. 2026-07-05 03:12 UTCEG score recompute
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 15:06 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 03:01 UTCEG score recompute
  13. 2026-07-03 14:42 UTCEG score recompute
  14. 2026-07-03 02:35 UTCEG score recompute
  15. 2026-07-02 14:30 UTCEG score recompute
  16. 2026-07-02 02:23 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 14:16 UTCEG score recompute
  19. 2026-07-01 02:10 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 14:05 UTCEG score recompute
  22. 2026-06-30 01:58 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 13:53 UTCEG score recompute
Show 18 more
  1. 2026-06-29 01:47 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 13:41 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 01:36 UTCEG score recompute
  7. 2026-06-27 13:30 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-27 01:24 UTCEG score recompute
  10. 2026-06-26 13:18 UTCEG score recompute
  11. 2026-06-26 01:12 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 13:05 UTCEG score recompute
  14. 2026-06-25 00:59 UTCEG score recompute
  15. 2026-06-24 12:53 UTCEG score recompute
  16. 2026-06-24 00:43 UTCEG score recompute
  17. 2026-06-23 12:37 UTCEG score recompute
  18. 2026-06-23 00:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52798?
CVE-2026-52798 is a high vulnerability published on June 22, 2026. Gogs is an open source self-hosted Git service. Prior to 0.14.3, although .ipynb previews are sanitized on the server side via /-/api/sanitize_ipynb, the inserted content is re-rendered on the client side without sanitization using marked() on elements with the .nb-markdown-cell class. During this…
When was CVE-2026-52798 disclosed?
CVE-2026-52798 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52798 actively exploited?
CVE-2026-52798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52798?
CVE-2026-52798 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-52798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52798, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52798

Explore →

Is Your Infrastructure Affected by CVE-2026-52798?

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