Advisories
This weekExploitable · Confirmed

railties: Use of Insufficiently Random Values in Railties Allows Remote Code Execution

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

railties (RubyGems)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • railties (RubyGems): from 5.2.0, before 5.2.2.1

The fix

  • railties (RubyGems) fixed in 5.2.2.1

    bundler
    bundle update --conservative railties
    Check what is installed
    bundle info railties
    Paste into Cursor, Lovable or Claude Code
    Upgrade the RubyGems dependency railties to 5.2.2.1 or the nearest later release, to fix CVE-2019-5420. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

  • Exploitable · Confirmed

    EPSS puts the chance of exploitation in the next 30 days at 89%.

    FIRST EPSSStated

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)