VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

sanitize: vulnerability history, versions and safety

sanitize is a package in the RubyGems ecosystem. Vulert records 4 vulnerabilities for it across 30 releases, from Mar 2018 to Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H3 M1
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 sanitize vulnerabilities

Vulert verdict on sanitize 7.0.1 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 7.0.1 — unaffected i
  • Vulnerabilities on record 4 over 5 years · 0 in the last year i
  • Latest disclosure 06 Jul 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 2,057 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 sanitize, 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
7.0.1 21 Oct 2026 none MIT — Details →
7.0.0 30 Dec 2024 none MIT — Details →
6.1.3 14 Aug 2024 none MIT — Details →
6.1.2 27 Jul 2024 none MIT — Details →
6.1.1 13 Jun 2024 none MIT — Details →
6.1.0 14 Sep 2023 none MIT — Details →
6.0.2 06 Jul 2023 none MIT — Details →
6.0.1 27 Jan 2023 H1 MIT Yes Details →
6.0.0 04 Aug 2021 H1 M1 MIT Yes Details →
5.2.3 11 Jan 2021 H1 M1 MIT Yes Details →
5.2.2 06 Jan 2021 H1 M1 MIT Yes Details →
5.2.1 16 Jun 2020 H1 M1 MIT Yes Details →
5.2.0 06 Jun 2020 H2 M1 MIT Yes Details →
5.1.0 08 Sep 2019 H2 M1 MIT Yes Details →
5.0.0 15 Oct 2018 H2 M1 MIT Yes Details →
2.1.1 30 Sep 2018 none — — Details →
4.6.6 24 Jul 2018 H2 MIT Yes Details →
4.6.5 17 May 2018 H2 MIT Yes Details →
4.6.4 20 Mar 2018 H2 MIT Yes Details →
4.6.3 20 Mar 2018 H2 MIT Yes Details →
4.6.2 19 Mar 2018 H3 MIT Yes Details →
4.6.1 15 Mar 2018 H3 MIT Yes Details →
4.6.0 30 Jan 2018 H3 MIT Yes Details →
4.5.0 04 Jun 2017 H3 MIT Yes Details →
4.4.0 30 Sep 2016 H3 MIT Yes Details →
4.3.0 20 Sep 2016 H3 MIT Yes Details →
4.2.0 23 Aug 2016 H3 MIT Yes Details →
4.1.0 17 Jul 2016 H3 MIT Yes Details →
4.0.1 09 Dec 2015 H3 MIT Yes Details →
4.0.0 20 Apr 2015 H3 MIT Yes Details →
3.1.2 22 Feb 2015 H3 MIT Yes Details →
3.1.1 04 Feb 2015 H3 MIT Yes Details →
3.1.0 23 Dec 2014 H3 MIT Yes Details →
3.0.4 12 Dec 2014 H3 MIT Yes Details →
3.0.3 29 Oct 2014 H3 MIT Yes Details →
3.0.2 03 Sep 2014 H3 MIT Yes Details →
3.0.1 03 Sep 2014 H3 MIT Yes Details →
3.0.0 21 Jun 2014 H3 MIT Yes Details →
2.1.0 13 Jan 2014 none — — Details →
2.0.6 11 Jul 2013 none — — Details →
2.0.5 10 Jul 2013 none — — Details →
2.0.4 12 Jun 2013 none — — Details →
2.0.3 02 Jul 2011 none — — Details →
2.0.3.dev.20110603 04 Jun 2011 none — — Details →
2.0.2 21 May 2011 none — — Details →
2.0.1 16 Mar 2011 none — — Details →
2.0.0 15 Jan 2011 none — — Details →
2.0.0.dev.20110105 06 Jan 2011 none — — Details →
2.0.0.dev.20101225 25 Dec 2010 none — — Details →
2.0.0.dev.20101213 14 Dec 2010 none — — Details →
2.0.0.dev.20101211 11 Dec 2010 none — — Details →
1.3.0.dev.20101210 11 Dec 2010 none — — Details →
1.2.2.dev.20101118 18 Nov 2010 none — — Details →
1.2.2.dev.20101028 29 Oct 2010 none — — Details →
1.2.2.dev.20100822 23 Aug 2010 none — — Details →
1.2.1 21 Apr 2010 none — — Details →
1.2.1.dev.20100329 30 Mar 2010 none — — Details →
1.2.1.dev.20100124 25 Jan 2010 none — — Details →
1.2.1.dev.20100122 23 Jan 2010 none — — Details →
1.2.0 17 Jan 2010 none — — Details →
1.2.0.dev.20091104 05 Nov 2009 none — — Details →
1.1.1.dev.20091102 02 Nov 2009 none — — Details →
1.1.0 11 Oct 2009 none — — Details →
1.0.0 25 Jul 2009 none — — Details →
1.0.1 25 Jul 2009 none — — Details →
1.0.2 25 Jul 2009 none — — Details →
1.0.3 25 Jul 2009 none — — Details →
1.0.4 25 Jul 2009 none — — Details →
1.0.5 25 Jul 2009 none — — Details →
1.0.6 25 Jul 2009 none — — Details →
1.0.7 25 Jul 2009 none — — Details →
1.0.8 25 Jul 2009 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 1
  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for sanitize

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-3740: Sanitize RubyGem Vulnerable to Improper Input Validation and Cross-site Scripting 7.5 high 4.6.3 21 Mar 2018
CVE-2020-4054: Cross-site Scripting in Sanitize 7.3 high 5.2.1 16 Jun 2020
CVE-2023-36823: Cross-site Scripting Vulnerability in sanitize RubyGem 7.1 high 6.0.2 06 Jul 2023
CVE-2023-23627: XSS Vulnerability in sanitize RubyGem 6.1 medium 6.0.1 28 Jan 2023

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 sanitize

Is sanitize safe to use?

Vulert records 4 vulnerabilities for sanitize in RubyGems: 0 critical, 3 high, 1 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 sanitize's Vulert package health score?

Vulert scores sanitize 80/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 sanitize affected?

No. 7.0.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.

How many vulnerabilities does sanitize have?

4 vulnerabilities are recorded for sanitize in the RubyGems ecosystem: 0 critical, 3 high, 1 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 sanitize vulnerabilities disclosed?

0 vulnerabilities were recorded for sanitize in the last 12 months, and the oldest entry in this database dates to 21 Mar 2018. 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 sanitize 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 sanitize for upcoming vulnerabilities?

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