CVE-2026-95112
Gitea issue reference parsing CPU exhaustion
Description
When processing issue and comment bodies, Gitea scanned the entire preceding text for action keywords such as "closes" or "fixes" once per Markdown link, giving processing time quadratic in the input size. An authenticated user able to submit issue or comment content could send a crafted body of about 1 MB that keeps a CPU core busy for several minutes while holding a database transaction open.
INFO
Published Date :
Oct. 6, 2026, 8:17 p.m.
Last Modified :
Oct. 6, 2026, 8:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Review and optimize issue/comment processing logic.
- Implement efficient text scanning for keywords.
- Limit input size for issues and comments.
- Release database transactions promptly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-95112.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-95112 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-95112
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-95112 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-95112 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2
Oct. 06, 2026
Action Type Old Value New Value Added Description When processing issue and comment bodies, Gitea scanned the entire preceding text for action keywords such as "closes" or "fixes" once per Markdown link, giving processing time quadratic in the input size. An authenticated user able to submit issue or comment content could send a crafted body of about 1 MB that keeps a CPU core busy for several minutes while holding a database transaction open. Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/95xxx/CVE-2026-95112.json">CVE-2026-95112</a> Added Reference https://blog.gitea.com/release-of-28.0.0/ Added Reference https://github.com/go-gitea/gitea/pull/39396 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-467c-4w7p-8427