dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-52815

MEDIUM · 5.5 CVSS v4.0 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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. Prior to 0.14.3, Gogs has an unauthenticated information disclosure vulnerability. The GET /api/v1/orgs/:orgname/teams endpoint at internal/route/api/v1/org_team.go:8 returns all teams for any organization without requiring authentication. The route group at internal/route/api/v1/api.go:380-385 lacks the reqToken() middleware, and the listTeams() handler performs no authentication check, exposing team IDs, names, descriptions, and permission levels to any unauthenticated caller. This vulnerability is fixed in 0.14.3.

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 prior to 0.14.3 contain an unauthenticated information disclosure vulnerability in the GET /api/v1/orgs/:orgname/teams endpoint. The route group at internal/route/api/v1/api.go lacks the reqToken() middleware, and the listTeams() handler performs no authentication check, allowing any unauthenticated caller to retrieve team IDs, names, descriptions, and permission levels for all organizations.

MitigationUpgrade Gogs to version 0.14.3 or later, which adds the required reqToken() middleware to enforce authentication on the affected endpoint.

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

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed Gogs version
    Check the Gogs admin panel under 'Site Administration' > 'System Info', or run 'gogs --version' from the binary, or check the installed package version via system package manager
    Affected if Version is 0.14.3 or lower (the vulnerability affects versions prior to 0.14.3)
  2. Verify API endpoint is accessible
    Make a GET request to http(s)://<your-gogs-server>/api/v1/orgs/:orgname/teams without providing any authentication token or session cookie
    Affected if The server responds with HTTP 200 instead of returning a 401 Unauthorized or 403 Forbidden error
  3. Inspect response for sensitive data exposure
    Examine the JSON response from the unauthenticated API call - look for team arrays containing id, name, description, and permission_access fields
    Affected if The response returns a non-empty list of teams with their IDs, names, descriptions, and permission levels for any organization without authentication
  4. Check if internal middleware is present
    Inspect the Gogs source file internal/route/api/v1/api.go around the orgs/:orgname/teams route definition - verify whether reqToken() middleware is present in the route registration
    Affected if The route handler is registered without the reqToken() middleware (this requires source code inspection if binary-only deployment)

You are affected if your Gogs version is prior to 0.14.3 AND the /api/v1/orgs/:orgname/teams endpoint returns team data without requiring authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gogs to version 0.14.3 or later, which adds the required reqToken() middleware to enforce authentication on the affected endpoint.

Recommended fix High confidence

0.14.3

  1. Upgrade Gogs to version 0.14.3 or later to address the unauthenticated information disclosure vulnerability
  2. After upgrading, verify that the GET /api/v1/orgs/:orgname/teams endpoint now requires authentication
  3. Confirm that the internal/route/api/v1/api.go route group now includes the reqToken() middleware for the teams endpoint
Caveat Review the Gogs 0.14.3 release notes for any breaking changes or migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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