Is multi_xml 0.0 vulnerable?

RubyGems · 1 release from 0.0.1 to 0.0.1 · latest multi_xml is 0.9.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. multi_xml 0.0.1, the last 0.0 release, is affected by 1 known security advisory (1 high), including CVE-2013-0175. Upgrade to 0.5.2 or later to fix all of them.

Upgrade with:bundle update --conservative multi_xml # Gemfile: '>= 0.5.2'

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

Advisories affecting multi_xml 0.0.1

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

    Improper Input Validation in multi_xml

    Affected
    <0.5.2
    Fixed in
    0.5.2

Which of your client projects are still on multi_xml 0.0?

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.