CVE-2025-64719: Gogs: Denial of Service in repository/wiki file listing web pages
Gogs is an open source self-hosted Git service. Prior to 0.14.3, 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. 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. This vulnerability is fixed in 0.14.3.
Security readout for executives and security teams
Plain-English summary
CVE-2025-64719 can make parts of a Gogs repository or wiki web interface stop working. An authorized user who can create a file can trigger HTTP 500 errors on file listing pages. This affects Gogs versions before 0.14.3 and is fixed in 0.14.3.
Executive priority
Treat as a moderate availability issue. Prioritize patching shared or business-critical Gogs instances, especially where many users have write access. This is not described as data theft or remote unauthenticated compromise in the provided sources.
Technical view
Gogs before 0.14.3 mishandles errors while recovering commit information in repository and wiki file listing paths. The affected code is reported in internal/route/repo/wiki.go and internal/route/repo/view.go. The impact is denial of service for affected listing pages, with no confidentiality or integrity impact reported.
Likely exposure
Exposure is limited to self-hosted Gogs instances running versions earlier than 0.14.3. The attacker must already have rights to create a new file in a repository or wiki page, so risk is higher in environments with many contributors or broad write permissions.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked as KEV. The attack is network reachable through the web application but requires high privileges. Successful exploitation affects availability of repository or wiki file listing pages.
Researcher notes
CVSS is 4.9 with AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H. The advisory maps the issue to CWE-20. The main validation focus is version exposure, contributor permissions, and whether file listing pages return 500 errors after commit information recovery failures.
Mitigation direction
Upgrade Gogs to version 0.14.3 or later.
Review and limit repository and wiki file creation permissions until upgraded.
Check the GitHub advisory for any additional vendor guidance.
Validation and detection
Inventory all self-hosted Gogs instances and record versions.
Confirm affected instances are upgraded to 0.14.3 or later.
Review which users can create repository or wiki files.
Monitor for repeated HTTP 500 errors on repository or wiki listing pages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.