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 36% 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.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

Published

June 23, 2026

Last Modified

June 26, 2026

Advisory Details (4)

Auto-updated Oct 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
githubMentions a patch (unverified)🟡 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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
gogs.io/gogs—
  • every version up to 0.14.3: fixed in 0.14.3
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 27× 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.

Showing the most recent 100 of 138 total refreshes for this CVE.

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

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 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 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52813?
CVE-2026-52813 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52813?
A fix for CVE-2026-52813 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52813 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.