0.0
NA
CVE-2026-96399
Gitea denial of service through external issue tracker patterns
Description

A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue references, causing a runtime panic that terminated the Gitea process. A user who can edit a repository's external issue tracker settings could make any later rendering of matching content, such as viewing a README, crash the instance for all users.

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
Affected Products

The following products are affected by CVE-2026-96399 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Gitea gitea
Solution
Update Gitea to fix a regex vulnerability in external issue trackers that causes panics.
  • Update Gitea to the latest version.
  • Review external issue tracker configurations.
  • Apply vendor patches 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-96399.

URL Resource
https://blog.gitea.com/release-of-28.0.0/
https://github.com/go-gitea/gitea/pull/39354
https://github.com/go-gitea/gitea/releases/tag/v28.0.0
https://github.com/go-gitea/gitea/security/advisories/GHSA-mw6q-qj47-9g5q
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-96399 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-96399 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-96399 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-96399 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 A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue references, causing a runtime panic that terminated the Gitea process. A user who can edit a repository's external issue tracker settings could make any later rendering of matching content, such as viewing a README, crash the instance for all users.
    Added CWE CWE-125
    Added CWE CWE-248
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/96xxx/CVE-2026-96399.json">CVE-2026-96399</a>
    Added Reference https://blog.gitea.com/release-of-28.0.0/
    Added Reference https://github.com/go-gitea/gitea/pull/39354
    Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.0.0
    Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-mw6q-qj47-9g5q
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.