Quick answers
- Is CVE-2026-52815 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52815 being exploited in the wild.
- How severe is CVE-2026-52815?
- Medium severity, with a CVSS score of 4, published 24 June 2026.
- Which products and versions are affected?
- gogs.io/gogs (Go) < 0.14.3, SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.14.3; Gogs < 0.14.3.
- Is there a fix for CVE-2026-52815?
- Yes. gogs.io/gogs (Go): upgrade to 0.14.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52815 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-52815?
- Check whether you run gogs.io/gogs (Go) or Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gogs.io/gogs (Go): upgrade to 0.14.3 or later
go get gogs.io/gogs@v0.14.3
Technical details
An unauthenticated information disclosure vulnerability exists in Gogs prior to version 0.14.3 due to missing authentication middleware on the organization teams API endpoint. Specifically, the route group for 'GET /api/v1/orgs/:orgname/teams' in 'internal/route/api/v1/api.go' lacks the 'reqToken()' middleware, and the 'ListTeams' handler in 'org_team.go' does not perform any authorization checks. An attacker can exploit this by sending a simple GET request to the affected endpoint to retrieve a JSON list of all teams within an organization, including their IDs, names, descriptions, and permission levels (e.g., read, write, admin, owner). This issue is resolved in version 0.14.3.
Affected products
- Gogs Gogs < 0.14.3
Identifiers
- CVE-2026-52815
- GHSA-744x-3838-5r56
- GO-2026-5202
Timeline
- 2026-06-19: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD