CVE-2026-52813

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1%, top 38% 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
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 10.0Exploit: 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, organization names containing path traversal sequences (../) are accepted by Gogs, and repositories under them are written to paths following these path traversals. This allows storing/retrieving data for repositories at arbitrary locations on the filesystem. By creating nested structure of Git repositories, one can overwrite the other's hooks configuration to result in Remote Code Execution (RCE). This vulnerability is fixed in 0.14.3.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
61.9%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 26, 2026

Advisory Details (4)

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

Path Traversal in organization name results in RCE through Git hooks · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-c39w-43gm-34h5
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: reject path traversal in owner and repository names

Fix merged in gogs/gogs PR #8334 on 2026-06-07 — awaiting tagged release

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

commit f6acd4673059 (gogs/gogs)

Fix landed in gogs/gogs commit f6acd4673059 — awaiting tagged release

https://github.com/gogs/gogs/commit/f6acd467305943aae8403cbac81f0118dd1235d7

Vendor Advisories for CVE-2026-52813(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 51× in last 7d / 98× 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 02:53 UTCEG score recompute
  2. 2026-07-06 23:03 UTCEG score recompute
  3. 2026-07-06 19:13 UTCEG score recompute
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 15:22 UTCEG score recompute
  7. 2026-07-06 11:23 UTCEG score recompute
  8. 2026-07-06 07:16 UTCEG score recompute
  9. 2026-07-06 03:17 UTCEG score recompute
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 23:16 UTCEG score recompute
  13. 2026-07-05 19:26 UTCEG score recompute
  14. 2026-07-05 15:36 UTCEG score recompute
  15. 2026-07-05 11:42 UTCEG score recompute
  16. 2026-07-05 07:50 UTCEG score recompute
  17. 2026-07-05 04:00 UTCEG score recompute
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 23:54 UTCEG score recompute
  20. 2026-07-04 20:04 UTCEG score recompute
  21. 2026-07-04 16:13 UTCEG score recompute
  22. 2026-07-04 12:20 UTCEG score recompute
  23. 2026-07-04 08:29 UTCEG score recompute
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-04 04:37 UTCEG score recompute
Show 73 more
  1. 2026-07-04 00:46 UTCEG score recompute
  2. 2026-07-03 20:40 UTCEG score recompute
  3. 2026-07-03 16:49 UTCEG score recompute
  4. 2026-07-03 12:54 UTCEG score recompute
  5. 2026-07-03 09:03 UTCEG score recompute
  6. 2026-07-03 05:13 UTCEG score recompute
  7. 2026-07-03 01:21 UTCEG score recompute
  8. 2026-07-02 21:31 UTCEG score recompute
  9. 2026-07-02 17:41 UTCEG score recompute
  10. 2026-07-02 13:43 UTCEG score recompute
  11. 2026-07-02 09:53 UTCEG score recompute
  12. 2026-07-02 06:03 UTCEG score recompute
  13. 2026-07-02 02:12 UTCEG score recompute
  14. 2026-07-01 22:21 UTCEG score recompute
  15. 2026-07-01 18:14 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 14:24 UTCEG score recompute
  18. 2026-07-01 10:32 UTCEG score recompute
  19. 2026-07-01 06:41 UTCEG score recompute
  20. 2026-07-01 02:50 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 22:59 UTCEG score recompute
  23. 2026-06-30 19:09 UTCEG score recompute
  24. 2026-06-30 15:19 UTCEG score recompute
  25. 2026-06-30 11:27 UTCEG score recompute
  26. 2026-06-30 07:34 UTCEG score recompute
  27. 2026-06-30 03:42 UTCEG score recompute
  28. 2026-06-29 23:47 UTCEG score recompute
  29. 2026-06-29 19:54 UTCEG score recompute
  30. 2026-06-29 16:04 UTCEG score recompute
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-29 14:06 UTCEPSS rescore
  33. 2026-06-29 12:12 UTCEG score recompute
  34. 2026-06-29 08:20 UTCEG score recompute
  35. 2026-06-29 04:30 UTCEG score recompute
  36. 2026-06-29 00:39 UTCEG score recompute
  37. 2026-06-28 20:49 UTCEG score recompute
  38. 2026-06-28 16:59 UTCEG score recompute
  39. 2026-06-28 14:07 UTCEPSS rescore
  40. 2026-06-28 13:09 UTCEG score recompute
  41. 2026-06-28 09:17 UTCEG score recompute
  42. 2026-06-28 05:27 UTCEG score recompute
  43. 2026-06-28 04:56 UTCEPSS rescore
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 01:36 UTCEG score recompute
  46. 2026-06-27 21:45 UTCEG score recompute
  47. 2026-06-27 17:55 UTCEG score recompute
  48. 2026-06-27 14:03 UTCEG score recompute
  49. 2026-06-27 10:12 UTCEG score recompute
  50. 2026-06-27 06:21 UTCEG score recompute
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-27 02:28 UTCEG score recompute
  53. 2026-06-26 22:37 UTCEG score recompute
  54. 2026-06-26 18:45 UTCEG score recompute
  55. 2026-06-26 14:55 UTCEG score recompute
  56. 2026-06-26 11:05 UTCEG score recompute
  57. 2026-06-26 03:03 UTCEG score recompute
  58. 2026-06-25 23:12 UTCEG score recompute
  59. 2026-06-25 19:21 UTCEG score recompute
  60. 2026-06-25 15:31 UTCEG score recompute
  61. 2026-06-25 13:49 UTCEPSS rescore
  62. 2026-06-25 11:40 UTCEG score recompute
  63. 2026-06-25 07:50 UTCEG score recompute
  64. 2026-06-25 03:59 UTCEG score recompute
  65. 2026-06-25 00:09 UTCEG score recompute
  66. 2026-06-24 20:17 UTCEG score recompute
  67. 2026-06-24 16:27 UTCEG score recompute
  68. 2026-06-24 12:36 UTCEG score recompute
  69. 2026-06-24 08:45 UTCEG score recompute
  70. 2026-06-24 04:55 UTCEG score recompute
  71. 2026-06-24 01:05 UTCEG score recompute
  72. 2026-06-23 21:14 UTCEG score recompute
  73. 2026-06-23 17:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52813?
CVE-2026-52813 is a critical vulnerability published on June 23, 2026. Gogs is an open source self-hosted Git service. Prior to 0.14.3, organization names containing path traversal sequences (../) are accepted by Gogs, and repositories under them are written to paths following these path traversals. This allows storing/retrieving data for repositories at arbitrary…
When was CVE-2026-52813 disclosed?
CVE-2026-52813 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52813 actively exploited?
CVE-2026-52813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 61.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52813?
CVE-2026-52813 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-52813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52813, 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-52813

Explore →

Is Your Infrastructure Affected by CVE-2026-52813?

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

Start Free Scan →Browse All CVEs