# CVE-2026-52813: Gogs: Path Traversal in organization name results in RCE through Git hooks

> Attackers can exploit path traversal in organization names to overwrite Git hooks, leading to remote code execution on the server.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-c39w-43gm-34h5, GO-2026-5305

## What is CVE-2026-52813?

CVE-2026-52813 is a critical path traversal vulnerability in gogs, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-52813?

3 open source packages ship an affected version, including gogs.io/gogs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gogs.io/gogs` | Go | All versions | None |
| `gogs.io/gogs` | Go | All versions | 0.14.3 |
| `gogs.io/gogs` | Go | All versions | 0.14.3 |

## How do I fix CVE-2026-52813?

Upgrade gogs.io/gogs to 0.14.3 or later.

## Is CVE-2026-52813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52813 exists.

Public exploit code:

- CVE-2026-52813 (Gogs Path Traversal → Git Hooks RCE) defensive writeup: root-cause & patch analysis, Sigma/SIEM detection rules, IOCs, non-intrusive version scanner. No weaponized PoC. (github_poc): https://github.com/iqx6889/CVE-2026-52813-Gogs-RCE

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52813 and fix it if it is affected.

What it is: CVE-2026-52813 is a critical path traversal vulnerability in gogs, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52813 exists.

Affected packages and fixed versions:
- gogs.io/gogs (Go): affected all versions; no fix listed
- gogs.io/gogs (Go): affected all versions; fixed in 0.14.3
- gogs.io/gogs (Go): affected all versions; fixed in 0.14.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52813/ (Markdown: https://insights.sbomify.com/CVE-2026-52813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52813
- OSV: https://osv.dev/vulnerability/CVE-2026-52813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52813/
Summaries are generated and may contain mistakes; the official description above is the record.