CVE
Gitea injection in RubyGems compact index via package metadata
Affects Gitea versions up to and including 28.2.0 when the package registry serves RubyGems packages. Fixed in 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 28.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Gitea package registry serving RubyGems packages (affected versions up to and including 28.2.0)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.17% · 6th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Gitea RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contained newline characters. A user who could publish a gem to an owner's registry could use this to forge compact index entries, making fake packages or extra versions of existing gems with attacker-chosen dependencies, which clients resolving from that registry could then install.
Original description
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.
Who should check
Teams running a Gitea instance as a RubyGems registry, and developers whose bundler clients resolve gems from it
“Affected versions <= 28.2.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Gitea package registry serving RubyGems packages (affected versions up to and including 28.2.0)Upgrade to a fixed version: 28.3.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118389 (Gitea RubyGems compact index injection through package metadata), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-118389 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: fixed in 28.3.0
Fixed versions: 28.3.0.
Conditions (all must be true for the bug to be hit):
- Gitea package registry serving RubyGems packages (affected versions up to and including 28.2.0) (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-118389 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118389 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq
- https://github.com/go-gitea/gitea/pull/39782
- https://github.com/go-gitea/gitea/pull/39900
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-118389
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118389"}.Timeline
- CVE published
- First seen by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 7
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Patch
- Patch
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118389
Is CVE-2026-118389 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Forged compact index entries can make Bundler clients resolve and install attacker-chosen dependencies. Those dependencies can include gems that run code on developer machines through install hooks.Source: github.com
Which versions are affected by CVE-2026-118389?
gitea.dev: before 28.3.0.Source: cve.now feed data
Am I affected, and how do I check?
Gitea versions up to and including 28.2.0 are affected when the package registry serves RubyGems packages. To check, look at the installed Gitea version and whether the RubyGems package registry is in use.Source: github.com
How do I fix CVE-2026-118389?
Upgrade Gitea to 28.3.0 or later, which is the fixed version listed for this vulnerability.Source: github.com