Vulnerability in gogs.io/gogs (CVE-2025-64719)
Summary
Vulnerability in gogs.io/gogs (CVE-2025-64719). Risk of unauthorized operations or information disclosure. Exploitable via view.go. Mitigation: upgrade to 0.14.3 or later.
Original description
The description as published by the source.
Summary
A malicious user with rights to create a new file on a repository or wiki page can trigger a denial of service condition in which the pages containing the listing of files will return HTTP error 500 and render the web interface unusable for the repository or wiki.
Details
The issue is present in file internal/route/repo/wiki.go and internal/route/repo/view.go where the pages try to recover commit information. If errors are returned while recovering commit information, the page will return a 500 error and stop rendering, resulting in a denial of service.
In view.go the issue occurs at line 56 while a slightly different issue occurs in wiki.go at line 174 where commits[0] is dereferenced without checking if it contains value.
It is possible to trigger issues in assigning the correct value to variable commits by using a specific string as part of the page title.
The issue is linked to the fact that file names can contain special characters such as *, ?, [, ], etc. that will be interpreted as git's pathspec instead of a simple string. So crafting a name containing an incomplete pathspec sequence will trigger this error.
PoC
As a proof of concept consider the file name "[] and how it affects repository and wiki pages.
I…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-64719 has been found in gogs.io/gogs.
Attackers can target a specific entry point like view.go over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade gogs.io/gogs to 0.14.3 or later.
If unsure, ask your IT team or search "gogs.io/gogs CVE-2025-64719" on the vendor's site.
CVE-2025-64719 (gogs.io/gogs) — CWE-20 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: view.go / wiki.go / commits
Patched: 0.14.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in gogs.io/gogs. Attackers reach the vulnerable code path via view.go.
Check the vendor advisory for the affected versions of gogs.io/gogs. Attack surface: view.go / wiki.go / commits.
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure.
Update to 0.14.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gogs.io/gogs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gogs.io/gogs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gogs.io/gogsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gogs.io/gogs to 0.14.3ステージング環境で 0.14.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web security-advisories@github.com
- web github.com
- web github.com
- web github.com
- web github.com