CVE-2026-118389: Gitea · Injection
Affects GiteaSource CVE Database V5
Not known to be exploited : upgrade to 28.3.0 soon.
Data as of 15 Nov 2026, 21:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 28.3.0
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 15 Nov 2026.
What to do
Upgrade Gitea to 28.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Giteagitea.dev | Affected
| Fixed in
|
AI-suggested
Upgrade Gitea to version 28.3.0 or later, where gems containing newline characters in platform, dependency names, or dependency version requirements are rejected, preventing index forgery. No other mitigation is required as the fix is official and complete.
Description
A vulnerability in Gitea allows injection via newline characters in RubyGems package metadata, enabling an attacker who can publish a gem to forge index entries. This could mislead clients into installing attacker-chosen dependencies. The issue is fixed in version 28.3.0, and gems with such metadata are now rejected.
References
- github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq (opens in a new tab)
- github.com/go-gitea/gitea/pull/39782 (opens in a new tab)
- github.com/go-gitea/gitea/pull/39900 (opens in a new tab)
- blog.gitea.com/release-of-28.4.0/ (opens in a new tab)
- github.com/go-gitea/gitea/releases/tag/v28.3.0 (opens in a new tab)