Skip to main content
VulnerabilityPublished

CVE-2026-118389: Gitea · Injection

Affects GiteaSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 28.3.0 soon.

Data as of 15 Nov 2026, 21:35 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 15 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade Gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • <28.3.0
Fixed in
  • 28.3.0

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

Community reviews

Loading reviews…