CVE-2026-23632

Vulnerability Description

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
• Execution of git push

As a result, a token with read-only permission can be used to modify repository contents.

Attack Prerequisites

• Possession of a valid access token
• Read permission on the target repository
  (public repository or collaborator with read access)

Attack Scenario

1. The attacker accesses the target repository with a read-only token
2. The attacker sends a PUT /contents request to update an arbitrary file
3. The server creates a commit and performs a git push on behalf of the attacker

Potential Impact

• Source code tampering
• Injection of backdoors
• Compromise of release artifacts and distributed packages

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-23632 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.13.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-23632? CVE-2026-23632 is a medium-severity missing authorization vulnerability in gogs.io/gogs (go), affecting versions <= 0.13.3. It is fixed in 0.13.4. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-23632? CVE-2026-23632 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of gogs.io/gogs are affected by CVE-2026-23632? gogs.io/gogs (go) versions <= 0.13.3 is affected.
4. Is there a fix for CVE-2026-23632? Yes. CVE-2026-23632 is fixed in 0.13.4. Upgrade to this version or later.
5. Is CVE-2026-23632 exploitable, and should I be worried? Whether CVE-2026-23632 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
6. What actually determines whether CVE-2026-23632 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.
7. How do I fix CVE-2026-23632? Upgrade gogs.io/gogs to 0.13.4 or later.