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

> Attackers can steal Gogs access tokens exposed in URLs via logs or referrers, potentially leading to unauthorized account access.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-x9p5-w45c-7ffc, GO-2026-4619

## What is CVE-2026-26196?

CVE-2026-26196 is a medium-severity vulnerability in gogs, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

## Which versions are affected by CVE-2026-26196?

3 open source packages ship an affected version, including gogs.io/gogs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gogs.io/gogs` | Go | All versions | None |
| `gogs.io/gogs` | Go | All versions to 0.13.3 | None |
| `gogs.io/gogs` | Go | All versions to 0.13.3 | None |

Products: Gogs Gogs.

## How do I fix CVE-2026-26196?

Upgrade to a fixed version.

## Is CVE-2026-26196 being exploited?

There is no known exploitation of CVE-2026-26196 in the wild and no public exploit code.

## Other vulnerabilities in gogs

- [CVE-2025-8110](https://insights.sbomify.com/CVE-2025-8110/): Gogs Path Traversal (high 8.7, exploited in the wild)
- [CVE-2024-56731](https://insights.sbomify.com/CVE-2024-56731/): Gogs deletion of internal files allows remote command execution (critical 10.0)
- [CVE-2022-1884](https://insights.sbomify.com/CVE-2022-1884/): Remote Command Execution in gogs/gogs (critical 10.0)
- [CVE-2022-1986](https://insights.sbomify.com/CVE-2022-1986/): OS Command Injection in gogs/gogs (critical 10.0)
- [CVE-2022-1992](https://insights.sbomify.com/CVE-2022-1992/): Path Traversal in gogs/gogs (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26196 and fix it if it is affected.

What it is: CVE-2026-26196 is a medium-severity vulnerability in gogs, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26196 in the wild and no public exploit code.

Affected packages and fixed versions:
- gogs.io/gogs (Go): affected all versions; no fix listed
- gogs.io/gogs (Go): affected all versions up to 0.13.3; no fix listed
- gogs.io/gogs (Go): affected all versions up to 0.13.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26196/ (Markdown: https://insights.sbomify.com/CVE-2026-26196/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26196
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26196
- OSV: https://osv.dev/vulnerability/CVE-2026-26196

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26196/
Summaries are generated and may contain mistakes; the official description above is the record.