gogs.io/gogs
Affected
- introduced
0, last affected0.13.3(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-26196, GO-2026-4619
Gogs: Access tokens get exposed through URL params in API requests
Summary
The Gogs API still accepts tokens in URL parameters such as token and access_token, which can leak through logs, browser history, and referrers.
Details
A static review shows that the API still checks tokens in the URL query before looking at headers:
c.Query("token")c.Query("access_token")Authorization header when the query token is emptyToken-authenticated requests are accepted by API routes through c.IsTokenAuth checks:
Impact
If tokens are sent in URLs such as /api/v1/user?token=..., they can leak in logs, browser or shell history, and referrer headers, and can be reused until revoked.
Recommended Fix
Remediation
A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2.
Medium Basis: The source's own band: MODERATE
0, last affected 0.13.3 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0