Gitea · Gitea · published 2026-11-15

CVE-2026-118389Gitea RubyGems compact index injection through package metadata

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-118389 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This Gitea vulnerability: CVSS 8.8 (v3.1), a successful attack gives total control of the component. Fixed upstream in Gitea 28.4.0, 28.3.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Gitea 28.4.0, 28.3.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security releases: 28.4.0, 28.3.0

    Upgrade to 28.4.028.3.0

    Why: Vendor security release for server software (most severe: CVE-2026-118389).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (30th pct)FIRST EPSS v2026.06.15
CVSS base score8.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries, such as packages that do not exist or additional versions of an existing gem with dependencies of their choice. Clients that resolve gems from that registry could then be led to install attacker-chosen dependencies. Gems with such metadata are now rejected.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →