Summary
Gogs vulnerable to arbitrary file deletion via Path Traversal in wiki page update
A Path Traversal vulnerability exists in the updateWikiPage function of Gogs. The vulnerability allows an authenticated user with write access to a repository's wiki to delete arbitrary files on the server by manipulating the old_title parameter in the wiki editing form.
Vulnerability Deatils
The vulnerability is located in internal/database/wiki.go. When updating a wiki page, the application accepts an old_title parameter to identify the potential rename operation. This parameter is used directly in path.Join and os.Remove without proper sanitization.
Code snippet from internal/database/wiki.go:
// Line 114
os.Remove(path.Join(localPath, oldTitle+".md"))
If an attacker provides a path traversal sequence (e.g., ../../../../target) as old_title, the os.Remove function will resolve the path relative to the wiki's local directory and delete the target file. The vulnerability is limited to deleting files that end with .md (due to the appended extension), but depending on the filesystem and specific path.Join behavior, or if critical .md files exist (e.g. documentation, other wikis), the impact is significant. Additionally, in some contexts, the extension might be bypassed or ignored.
Reproduction Steps
- Log in to Gogs as a user with write access to a repository wiki.
- Intercept the
POSTrequest to/repo/wiki/edit. - Modify the
old_titleparameter to../../../../tmp/target_file. - Submit the request.
- Observe that
/tmp/target_file.mdis deleted from the server.
Impact
- Denial of Service: Deletion of critical configuration files or data (if they match the extension or via other tricks).
- Data Loss: Deletion of other users' wiki pages or documentation.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Sanitize the oldTitle parameter using ToWikiPageName (or path.Clean and basename validation) before using it in file operations, similar to how the new title is currently handled.
// Recommended Fix
if oldTitle != "" {
oldTitle = ToWikiPageName(oldTitle)
}
Frequently Asked Questions
- What is CVE-2026-24135? CVE-2026-24135 is a high-severity path traversal vulnerability in gogs.io/gogs (go), affecting versions <= 0.13.3. It is fixed in 0.13.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of gogs.io/gogs are affected by CVE-2026-24135? gogs.io/gogs (go) versions <= 0.13.3 is affected.
- Is there a fix for CVE-2026-24135? Yes. CVE-2026-24135 is fixed in 0.13.4. Upgrade to this version or later.
- Is CVE-2026-24135 exploitable, and should I be worried? Whether CVE-2026-24135 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-24135 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-24135? Upgrade
gogs.io/gogsto 0.13.4 or later.