Skip to main content
CVE-2026-58428VulnerabilityPublished 07/22/2026Updated 08/14/2026

CVE-2026-58428: Gitea Open Source Git Server · CWE-424

Affects Gitea Gitea Open Source Git ServerSource GCVE Database

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.5 Medium · fixed in 1.27.0 : update Gitea Open Source Git Server when convenient.

Data as of 10/25/2026, 16:58:56 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.27.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Gocode.gitea.io/giteaAffected
  • <1.27.0
Fixed in
  • 1.27.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that fixes this issue by ensuring the web release edit form validates attachment file extensions against the allowlist before updating the database. Users should upgrade to Gitea version 1.27.0 or later to remediate this vulnerability.

Description

Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939)

Impact

The vulnerability allows users with repository write permissions to bypass configured restrictions on release attachment file extensions via the web interface. While it does not directly impact confidentiality or availability, it can lead to integrity issues by allowing disallowed file types to be associated with releases. This could facilitate the distribution of malicious or unauthorized files within the repository context.

Weaknesses

References

Community reviews

Loading reviews…