CVE-2026-23632: Gogs user can update repository content with read-only permission

Published Feb 6, 2026
·
Updated

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

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
gogs<=0.13.3
go/gogs.io/gogs<=0.13.3
0.13.4
Gogs Gogs<0.13.4

Event History

Feb 6, 2026
CVE Published
via MITRE·05:43 PM
Data Sourced
via MITRE·05:43 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:10 PM
Data Sourced
via GitHub·06:10 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
Affected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-23632?

CVE-2026-23632 is classified as a high severity vulnerability due to its potential for unauthorized access and modification of repository content.

2

How do I fix CVE-2026-23632?

To fix CVE-2026-23632, upgrade Gogs to version 0.13.4 or later, which includes a patch for this vulnerability.

3

What is the impact of CVE-2026-23632?

The impact of CVE-2026-23632 allows users with read-only permissions to edit repository contents, potentially leading to data integrity issues.

4

Which versions of Gogs are affected by CVE-2026-23632?

CVE-2026-23632 affects Gogs versions prior to 0.13.4, specifically up to version 0.13.3.

5

How does CVE-2026-23632 exploit permissions in Gogs?

CVE-2026-23632 exploits a flaw where the `PUT /repos/:owner/:repo/contents/*` endpoint does not adequately enforce write permissions, allowing unauthorized content updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203