dbcve.org
GogsApplication

CVE-2026-23632

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 0.13.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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, the endpoint "PUT /repos/:owner/:repo/contents/*" does not require write permissions and allows access with read permission only via repoAssignment(). After passing the permission check, PutContents() invokes UpdateRepoFile(), which results in commit creation and the execution of git push. As a result, a token with read-only permission can be used to modify repository contents. 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

Gogs versions 0.13.3 and prior contain an insecure direct object reference in the PUT /repos/:owner/:repo/contents/* endpoint. The permission check via repoAssignment() incorrectly allows read-only tokens to pass, enabling PutContents() to invoke UpdateRepoFile() and create commits with git push, bypassing the write permission requirement.

MitigationUpgrade Gogs to version 0.13.4 or 0.14.0+dev to patch the permission bypass. Alternatively, audit and revoke existing read-only tokens until upgrade is complete.

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
None

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

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
    Run 'gogs --version' or check the admin dashboard under 'System Admin > Info' to find the exact version number
    Affected if The version is 0.13.3 or lower (anything below 0.13.4)
  2. Identify existing API tokens
    Navigate to User Settings > Applications > Token (or query the database table 'access_token' if direct database access is available) to list all API tokens
    Affected if Any read-only or write-access tokens exist in the system
  3. Audit recent commits for API origin
    Review repository commit logs and check the 'Committer' or 'Author' field - API-based commits often show an API token name or generic API identifier rather than a real username
    Affected if Commits exist that were authored by token names or show unexpected origins matching API token identifiers
  4. Verify token permission scopes
    Examine each access token's granted scopes in the Gogs admin panel or database - look for tokens with 'read' or 'repository' scope that should not have write permissions
    Affected if Any token has only 'read' permissions but commits were created using that token

You are affected if your Gogs version is below 0.13.4 AND you have API tokens in use, as the vulnerability allows read-only tokens to bypass write permission checks on the repository contents endpoint.

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 patch the permission bypass. Alternatively, audit and revoke existing read-only tokens until upgrade is complete.

Recommended fix High confidence

Gogs 0.13.4 or later (0.14.0+dev)

  1. 1. Back up your Gogs data directory (usually /home/gogs/gogs) and configuration file
  2. 2. Stop the Gogs service
  3. 3. Download and install Gogs version 0.13.4 or later from the official repository (e.g., https://gogs.io)
  4. 4. Ensure the upgrade preserves your existing data and configuration
  5. 5. Start the Gogs service
  6. 6. Verify that the authorization fix is working by testing that read-only tokens can no longer modify repository contents
Caveat Review the release notes for version 0.13.4 to check for any breaking changes from your current version before upgrading

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

Fix this in Gogs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23632 — 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-23632 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