https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 16:30:35 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-06148 bdu:2026-06148 https://cve.radiocsirt.org/vuln/bdu:2026-06148 https://cve.radiocsirt.org/vuln/euvd-2026-274836 EUVD-2026-274836 https://cve.radiocsirt.org/vuln/euvd-2026-274836 https://cve.radiocsirt.org/vuln/fkie_cve-2026-26196 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-26196 https://cve.radiocsirt.org/vuln/ghsa-x9p5-w45c-7ffc <p><strong>Affected:</strong> Go: gogs.io/gogs</p> <p>### Summary</p> <p>The Gogs API still accepts tokens in URL parameters such as `token` and `access_token`, which can leak through logs, browser history, and referrers.</p> <p>### Details</p> <p>A static review shows that the API still checks tokens in the URL query before looking at headers:</p> <p>- internal/context/auth.go reads `c.Query(&#34;token&#34;)` - internal/context/auth.go falls back to `c.Query(&#34;access_token&#34;)` - 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</p> <p>Token-authenticated requests are accepted by API routes through `c.IsTokenAuth` checks: - internal/route/api/v1/api.go</p> <p>### Impact</p> <p>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.</p> <p>### Recommended Fix</p> <p>- 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.</p> <p>### Remediation</p> <p>A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2.</p> <p><strong>Affected:</strong> Go: gogs.io/gogs</p> <p>### Summary</p> <p>The Gogs API still accepts tokens in URL parameters such as `token` and `access_token`, which can leak through logs, browser history, and referrers.</p> <p>### Details</p> <p>A static review shows that the API still checks tokens in the URL query before looking at headers:</p> <p>- internal/context/auth.go reads `c.Query(&#34;token&#34;)` - internal/context/auth.go falls back to `c.Query(&#34;access_token&#34;)` - 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</p> <p>Token-authenticated requests are accepted by API routes through `c.IsTokenAuth` checks: - internal/route/api/v1/api.go</p> <p>### Impact</p> <p>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.</p> <p>### Recommended Fix</p> <p>- 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.</p> <p>### Remediation</p> <p>A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2.</p> https://cve.radiocsirt.org/vuln/ghsa-x9p5-w45c-7ffc https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0623 <p>Ein Angreifer kann mehrere Schwachstellen in Gogs ausnutzen, um Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Gogs ausnutzen, um Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0623