Is i18n 0.4 vulnerable?

RubyGems · 3 releases from 0.4.0 to 0.4.2 · latest i18n is 1.15.2 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. i18n 0.4.2, the last 0.4 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2014-10077, CVE-2013-4492. Upgrade to 0.8.0 or later to fix all of them.

Upgrade with:bundle update --conservative i18n # Gemfile: '>= 0.8.0'

Is your project on an affected i18n?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting i18n 0.4.2

  • HighCVE-2014-10077GHSA-34hf-g744-jw6414 May 2022

    i18n Vulnerable to Denial of Service Attack

    Affected
    <0.8.0
    Fixed in
    0.8.0
  • MediumCVE-2013-4492GHSA-r5hc-9xx5-97rw24 Oct 2017

    i18n gem Cross-site Scripting vulnerability

    Affected
    <0.6.6
    Fixed in
    0.6.6

Every i18n 0.4.x release

Affected: 0.4.0 to 0.4.2. Latest i18n: 1.15.2.

VersionKnown advisories
i18n 0.4.2CVE-2014-10077, CVE-2013-4492
i18n 0.4.1CVE-2014-10077, CVE-2013-4492
i18n 0.4.0CVE-2014-10077, CVE-2013-4492

Which of your client projects are still on i18n 0.4?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact i18n version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other i18n versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.