Servers and applications
CVE-2026-26196
Access tokens get exposed through URL params in API requests
- Severity
- Medium 6.9
- Published
- 5 Mar 2026
- Last changed
- 17 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 0.14.2
- Exploit chance
- 0.3% in the next 30 daysHigher than 22% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-598
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data
- CVSS vector
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:X/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- Also known as
- GHSA-x9p5-w45c-7ffc
- Sources
- NVD, Project advisories (GitHub)
Description
gogs api still accepts tokens in url params like token and access_token, which can leak through logs, browser history, and referrers
static review shows the api still checks tokens in the url query before looking at headers
- internal/context/auth.go reads c.Query("token")
- internal/context/auth.go falls back to c.Query("access_token")
- internal/context/auth.go only checks authorization header when query token is empty
- internal/context/auth.go authenticates using that token and marks request as token-authenticated
token authenticated requests are accepted by API routes through c.IsTokenAuth checks
- internal/route/api/v1/api.go
if users send tokens in urls like /api/v1/user?token=..., they can leak in logs, browser or shell history, and referrer headers, and can be reused until revoked
Affected software
| Software | Affected versions |
|---|---|
GogsServers and applications · cpe:a:gogs:gogs |
|
GogsServers and applications · github:gogs/gogs |
|
About Gogs
free forge based on Git written in Go
- Docker Hub pulls
- 94,040,857Docker Hub, 15 Nov 2026
- GitHub stars
- 47,939GitHub, 15 Nov 2026
- Forks
- 5,082GitHub, 15 Nov 2026
- Latest release
- v0.14.4GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- Developer
- FLOSS contributorWikidata
- License
- Expat licenseWikidata
- Written in
- Go, Cascading Style Sheets, JavaScriptWikidata
- First released
- 11 Feb 2014Wikidata
- First published on GitHub
- 12 Feb 2014GitHub
Website Source code Docker image
Vulnerabilities in Gogs
- In our list
- 88
- Published in the last 12 months
- 54
- Critical, last 12 months
- 5
- High, last 12 months
- 23
- Known exploited
- 1
- CVE-2026-133113Gogs through 0.14.4 Protected Branch Allowlist Bypass via Pull Request MergeHigh 7.1 19 Nov 2026
- GHSA-8r2x-49gj-h6rmProtected Branch Bypass via Pull Request Merge Due to Missing Hook Environment VariablesHigh 8.3 18 Nov 2026
- GHSA-7cvr-7cff-2mrgLDAP login selects the local account by email while the directory identity is searched by uid: an unrelated directory entry whose uid attribute equals a victim's Gogs email authenticates as that account - including site adminsMedium 18 Nov 2026
- GHSA-6972-pq3q-8w9rStored cross-site scripting in Gogs commit subjects through the external issue tracker formatHigh 8.7 18 Nov 2026
- GHSA-f9vc-qvc8-p7cfTwo-factor authentication bypass in the Gogs web API through a leading-slash path mismatchHigh 8.1 18 Nov 2026
- GHSA-p27c-f9fr-4jmwRemote process crash in Gogs diff rendering via a quoted rename pathHigh 7.5 16 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-26196
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-26196
- GitHub Advisory Database https://github.com/advisories/GHSA-x9p5-w45c-7ffc
- github.com https://github.com/gogs/gogs/security/advisories/GHSA-x9p5-w45c-7ffc