API token disclosure via query-string authentication
Published Mar 5, 2026 · Updated Mar 5, 2026
Sensitive query-string exposure in Gogs before 0.14.2 allows attackers to recover reusable API access tokens from URL-bearing records. The API authentication path in internal/context/auth.go reads token and access_token query parameters before examining the Authorization header, placing credentials in URLs retained by logs, browser or shell history, and referrer headers. Access to one of those records is required; a recovered token grants its owner's API permissions until revoked.
Summary
What happened
Sensitive query-string exposure in Gogs before 0.14.2 allows attackers to recover reusable API access tokens from URL-bearing records. The API authentication path in internal/context/auth.go reads token and access_token query parameters before examining the Authorization header, placing credentials in URLs retained by logs, browser or shell history, and referrer headers. Access to one of those records is required; a recovered token grants its owner's API permissions until revoked.
The record
- CVE
- CVE-2026-26196
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- Gogs
- Product
- Gogs
- Classifications
- CWE-598, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.14.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo