How severe is GHSA-x9p5-w45c-7ffc?

GHSA-x9p5-w45c-7ffc has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-x9p5-w45c-7ffc?

GHSA-x9p5-w45c-7ffc affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix GHSA-x9p5-w45c-7ffc?

No patched version of gogs.io/gogs has shipped for GHSA-x9p5-w45c-7ffc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-x9p5-w45c-7ffc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-x9p5-w45c-7ffc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x9p5-w45c-7ffc?

O3 pinpoints whether GHSA-x9p5-w45c-7ffc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x9p5-w45c-7ffc actively exploited in the wild?

No public exploit code has been indexed for GHSA-x9p5-w45c-7ffc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x9p5-w45c-7ffc?

GHSA-x9p5-w45c-7ffc has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x9p5-w45c-7ffc?

GHSA-x9p5-w45c-7ffc is classified as CWE-598 (CWE-598). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x9p5-w45c-7ffc published, and has it been updated?

GHSA-x9p5-w45c-7ffc was published on March 5, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-x9p5-w45c-7ffc

MEDIUM

Gogs: Access tokens get exposed through URL params in API requests

Also known asCVE-2026-26196GO-2026-4619

Published

Mar 5, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk17th percentile+0.21%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹gogs.io/gogs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

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 the Authorization header when the query token is empty
internal/context/auth.go authenticates using that token and marks the request as token-authenticated

Token-authenticated requests are accepted by API routes through c.IsTokenAuth checks:

internal/route/api/v1/api.go

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

Authentication headers should be used exclusively for token transmission.
Token parameters should be blocked at the proxy or WAF level.
Query strings should be scrubbed from logs.
A strict referrer policy should be set.

Remediation

A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gogs.io/gogs`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of gogs.io/gogs has shipped for GHSA-x9p5-w45c-7ffc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x9p5-w45c-7ffc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x9p5-w45c-7ffc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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: - 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 the `Authorization` header when the query token is empty - internal/context/auth.go authenticates using that token and marks the request as token-authenticate

O3 Security · Impact-Aware SCA

Is GHSA-x9p5-w45c-7ffc in your dependencies?

O3 detects GHSA-x9p5-w45c-7ffc across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works