dbcve.org
GogsApplication

CVE-2026-24135

HIGH · 8.1 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 0.13.4 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Gogs is an open source self-hosted Git service. In version 0.13.3 and prior, 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. This issue has been patched in versions 0.13.4 and 0.14.0+dev.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in Gogs versions 0.13.3 and prior allows authenticated users with wiki write access to delete arbitrary files on the server by manipulating the old_title parameter in the updateWikiPage function. The attack leverages insufficient input validation to traverse beyond the intended wiki directory.

MitigationUpgrade Gogs to version 0.13.4 or 0.14.0+dev to obtain the patch, and restrict repository wiki write permissions to trusted users until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GogsApplication
Affected:< 0.13.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Gogs version
    Check the Gogs version by accessing the admin dashboard or running 'gogs --version' from the command line if accessible.
    Affected if The installed version is 0.13.3 or prior (anything less than 0.13.4).
  2. Verify wiki feature is enabled
    Check Gogs configuration files or admin settings to confirm the wiki module is enabled for repositories.
    Affected if Wiki functionality is enabled and accessible to users.
  3. Review wiki write permissions
    Inspect repository settings and user role assignments to determine which users have write access to wiki pages.
    Affected if Any user account (other than fully trusted administrators) has wiki write permissions.
  4. Check for suspicious wiki page deletions
    Review Gogs audit logs or repository activity logs for deletion operations on wiki pages, particularly those occurring outside expected patterns.
    Affected if There are wiki page deletion events that correspond to unexpected file paths or unusual activity.

A user is affected if they run Gogs version 0.13.3 or prior AND have the wiki feature enabled with any untrusted user accounts possessing wiki write access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.13.4 or later
Fixed in 0.13.4
Interim mitigation

Upgrade Gogs to version 0.13.4 or 0.14.0+dev to obtain the patch, and restrict repository wiki write permissions to trusted users until the upgrade is applied.

Recommended fix High confidence

0.13.4 or later (0.14.0+dev)

  1. 1. Check the current Gogs version by running `gogs --version` or checking the admin dashboard
  2. 2. If version is less than 0.13.4, plan the upgrade to version 0.13.4 or later
  3. 3. Backup the Gogs data directory (contains repositories, user data, and configuration)
  4. 4. Stop the Gogs service
  5. 5. Download Gogs version 0.13.4 or later from the official GitHub releases (github.com/gogs/gogs/releases)
  6. 6. Replace the existing Gogs binary with the new version
  7. 7. Start the Gogs service
  8. 8. Verify the upgrade was successful by checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gogs Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data