# CVE-2026-23633: Gogs has arbitrary file read/write via path traversal in Git hook editing

> Attackers can read or write arbitrary files via path traversal in Git hook editing, compromising the Gogs self-hosted Git service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-mrph-w4hh-gx3g, GO-2026-4453

## What is CVE-2026-23633?

CVE-2026-23633 is a medium-severity path traversal vulnerability in gogs, published on 6 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Gogs is an open source self-hosted Git service. In version 0.13.3 and prior, there is an arbitrary file read/write via path traversal in Git hook editing. This issue has been patched in versions 0.13.4 and 0.14.0+dev.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including gogs.io/gogs. It affects 1 product.


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

Products: Gogs Gogs.

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

Upgrade gogs.io/gogs to 0.13.4 or later.

## Is CVE-2026-23633 being exploited?

There is no known exploitation of CVE-2026-23633 in the wild and no public exploit code.

## Other vulnerabilities in gogs

- [CVE-2025-8110](https://insights.sbomify.com/CVE-2025-8110/): Gogs Path Traversal (high 8.7, exploited in the wild)
- [CVE-2024-56731](https://insights.sbomify.com/CVE-2024-56731/): Gogs deletion of internal files allows remote command execution (critical 10.0)
- [CVE-2022-1884](https://insights.sbomify.com/CVE-2022-1884/): Remote Command Execution in gogs/gogs (critical 10.0)
- [CVE-2022-1986](https://insights.sbomify.com/CVE-2022-1986/): OS Command Injection in gogs/gogs (critical 10.0)
- [CVE-2022-1992](https://insights.sbomify.com/CVE-2022-1992/): Path Traversal in gogs/gogs (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23633 is a medium-severity path traversal vulnerability in gogs, published on 6 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23633 in the wild and no public exploit code.

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.13.4
- gogs.io/gogs (Go): affected all versions; fixed in 0.13.4

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-23633/ (Markdown: https://insights.sbomify.com/CVE-2026-23633/index.md)
```

## Sources

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

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