VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

multi_xml: vulnerability history, versions and safety

multi_xml is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 17 releases, first recorded in Oct 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all multi_xml vulnerabilities

Vulert verdict on multi_xml 0.9.1 i

Updated on 23 Oct 2026

Good news: 0.9.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.9.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.9.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.9.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Oct 2017 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 171 i
  • OpenSSF scorecard 3/10 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for multi_xml, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.9.1 04 May 2026 none MIT — Details →
0.9.0 02 May 2026 none MIT — Details →
0.8.1 08 Jan 2026 none MIT — Details →
0.8.0 24 Dec 2025 none MIT — Details →
0.7.2 30 Apr 2025 none MIT — Details →
0.7.1 01 May 2024 none MIT — Details →
0.7.0 30 Apr 2024 none MIT — Details →
0.6.0 06 Dec 2016 none MIT — Details →
0.5.5 06 Aug 2013 none MIT — Details →
0.5.4 04 Jun 2013 none MIT — Details →
0.5.3 08 Feb 2013 none MIT — Details →
0.5.2 11 Jan 2013 none MIT — Details →
0.5.1 10 May 2012 H1 — Yes Details →
0.5.0 08 May 2012 H1 — Yes Details →
0.4.4 16 Apr 2012 H1 — Yes Details →
0.4.3 16 Apr 2012 H1 — Yes Details →
0.4.2 12 Mar 2012 H1 — Yes Details →
0.4.1 26 Sep 2011 H1 — Yes Details →
0.4.0 06 Sep 2011 H1 — Yes Details →
0.3.0 08 Aug 2011 H1 — Yes Details →
0.2.2 20 Mar 2011 H1 — Yes Details →
0.2.1 03 Feb 2011 H1 — Yes Details →
0.2.0 22 Oct 2010 H1 — Yes Details →
0.1.4 20 Oct 2010 H1 — Yes Details →
0.1.3 19 Oct 2010 H1 — Yes Details →
0.1.2 16 Oct 2010 H1 — Yes Details →
0.1.1 16 Oct 2010 H1 — Yes Details →
0.1.0 12 Oct 2010 H1 — Yes Details →
0.0.1 03 Oct 2010 H1 — Yes Details →

All 29 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for multi_xml

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-0175: Improper Input Validation in multi_xml N/A high 0.5.2 24 Oct 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About multi_xml

Is multi_xml safe to use?

Vulert records 1 vulnerabilities for multi_xml in RubyGems: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is multi_xml's Vulert package health score?

Vulert scores multi_xml 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of multi_xml affected?

No. 0.9.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of multi_xml should I use?

0.9.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does multi_xml have?

1 vulnerability is recorded for multi_xml in the RubyGems ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new multi_xml vulnerabilities disclosed?

0 vulnerabilities were recorded for multi_xml in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of multi_xml are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor multi_xml for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the multi_xml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.