Is multi_xml 0.5 vulnerable?

RubyGems · 6 releases from 0.5.0 to 0.5.5 · latest multi_xml is 0.9.1 · checked 18 Nov 2026

No known advisories in the last release

multi_xml 0.5.5, the last 0.5 release, has no known advisories. 1 advisory affects earlier 0.5.x releases, so update to 0.5.5.

Update within 0.5:bundle update --conservative multi_xml # Gemfile: '>= 0.5.5'

Is your project on an affected multi_xml?

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

Fixed within 0.5.x, affecting earlier releases

  • HighCVE-2013-0175GHSA-pchc-949f-53m524 Oct 2017

    Improper Input Validation in multi_xml

    Affected
    <0.5.2
    Fixed in
    0.5.2

Every multi_xml 0.5.x release

Affected: 0.5.0 to 0.5.1. 0.5.2 and later are not affected. Latest multi_xml: 0.9.1.

VersionKnown advisories
multi_xml 0.5.5None
multi_xml 0.5.4None
multi_xml 0.5.3None
multi_xml 0.5.2None
multi_xml 0.5.1CVE-2013-0175
multi_xml 0.5.0CVE-2013-0175

Which of your client projects are still on multi_xml 0.5?

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

Other multi_xml 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.