Technical impact
The vulnerability allows a user who can publish a gem to a Gitea‑hosted registry to include newline characters in the gem’s platform, dependency names, or dependency version requirements. Because the compact index the registry serves to clients is line‑based, these newlines enable forging of index entries, such as non‑existent packages or additional versions of existing gems. A client resolving gems from the registry may then install attacker‑chosen dependencies, potentially leading to arbitrary code execution. The weakness is a classic form of input tampering and is classified as CWE‑74.
Affected Systems
The affected product is the Gitea platform. Versions prior to the release of 28.4.0 are susceptible, as the update in that release introduces validation that rejects gems containing metadata with newline characters. The issue was addressed in the 28.4.0 release and later versions.
Risk and Exploitability
A successful exploit requires the attacker to have publish rights to a registry that belongs to a repository owner. Once a malicious gem is uploaded, clients that resolve gems from that registry will be forced to install the attacker-specified dependencies, which can include malicious code. Although an EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, the nature of the impact—forced installation of arbitrary dependencies—indicates a high severity scenario, especially in environments where repository owners have broad publish privileges.