Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A brass combination padlock resting on a white keyboard beside gold payment cards.

    Gitea 28.3.0 fixes RubyGems index poisoning flaw (CVE-2026-118389)

    Gitea

    What's fixed

    Gitea's package registry accepts RubyGems packages whose platform, dependency name or version requirement fields contain newline characters. The compact index is line-based, so an attacker can forge phantom entries in /versions and fake version entries in info/<name>. A developer whose Gemfile names a real package can then get the attacker's gem installed by bundler as a transitive dependency.

    The advisory rates it high, CVSS 8.1, with a network vector, low privileges and no user interaction. Attacker code can run on developer machines through gem install hooks, and the victim sees nothing odd because the Gemfile names a real package. Gitea 28.2.0 and earlier are affected, and 28.3.0 is the patched version. The advisory does not say whether the flaw is exploited in the wild.

    What to do

    If your Gitea instance hosts RubyGems packages, update to 28.3.0. The fix, commit c52e7c0c, rejects \r and \n in those metadata fields before they are stored. No workaround for unpatched instances is given, so updating is the only listed remedy.

    Product Affected Fixed
    Gitea <= 28.2.0 28.3.0

    Sources

    Image: Photo by Towfiqu barbhuiya on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion