VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

mail: vulnerability history, versions and safety

mail is a package in the RubyGems ecosystem. Vulert records 5 vulnerabilities for it across 96 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H1 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 02 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mail vulnerabilities

Vulert verdict on mail 2.9.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.9.1 — unaffected i
  • Vulnerabilities on record 5 over 8 years · 1 in the last year i
  • Latest disclosure 02 Sep 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 3,671 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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 mail, 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
2.9.1 01 Jul 2026 none MIT — Details →
2.9.0 22 Oct 2025 M1 MIT Yes Details →
2.9.0.beta2 20 Mar 2025 M1 MIT Yes Details →
2.9.0.beta1 20 Mar 2025 M1 MIT Yes Details →
2.8.1 03 Feb 2023 M1 MIT Yes Details →
2.8.1.rc2 18 Jan 2023 M1 MIT Yes Details →
2.8.0.1 12 Jan 2023 M1 MIT Yes Details →
2.8.0.1.rc1 12 Jan 2023 M1 MIT Yes Details →
2.8.0 03 Dec 2022 M1 MIT Yes Details →
2.8.0.rc3 30 Nov 2022 M1 MIT Yes Details →
2.8.0.rc2 30 Nov 2022 M1 MIT Yes Details →
2.8.0.rc1 22 Apr 2022 M1 MIT Yes Details →
2.7.1 13 Oct 2018 M1 MIT Yes Details →
2.7.1.rc1 01 Mar 2018 M1 MIT Yes Details →
2.7.0 01 Nov 2017 M1 MIT Yes Details →
2.7.0.rc3 29 Oct 2017 M1 MIT Yes Details →
2.7.0.rc2 24 Oct 2017 M1 MIT Yes Details →
2.5.5 09 Jun 2017 M1 MIT Yes Details →
2.6.6 09 Jun 2017 M1 MIT Yes Details →
2.7.0.rc1 09 May 2017 M1 MIT Yes Details →
2.6.6.rc1 09 May 2017 M1 MIT Yes Details →
2.5.5.rc1 09 May 2017 M2 MIT Yes Details →
2.6.5 27 Apr 2017 M1 MIT Yes Details →
2.6.5.rc1 07 Apr 2017 M1 MIT Yes Details →
2.6.4 23 Mar 2016 M1 MIT Yes Details →
2.6.4.rc2 14 Jan 2016 M1 MIT Yes Details →
2.6.4.rc1 17 Dec 2015 M1 MIT Yes Details →
2.6.3 03 Nov 2014 M1 MIT Yes Details →
2.6.1 08 Jun 2014 M1 MIT Yes Details →
2.6.0 02 Jun 2014 M1 MIT Yes Details →
2.5.4 14 May 2013 M2 MIT Yes Details →
2.2.20 14 May 2013 H1 M3 — Yes Details →
2.5.3 04 Dec 2012 M2 — Yes Details →
2.5.2 18 Nov 2012 M2 — Yes Details →
2.4.4 14 Mar 2012 M2 — Yes Details →
2.3.3 14 Mar 2012 H1 M3 — Yes Details →
2.3.2 06 Mar 2012 H1 M3 — Yes Details →
2.4.3 06 Mar 2012 M3 — Yes Details →
2.4.1 20 Jan 2012 H1 M3 — Yes Details →
2.4.0 15 Jan 2012 H1 M3 — Yes Details →
2.3.0 26 Apr 2011 H1 M3 — Yes Details →
2.2.19 26 Apr 2011 H1 M3 — Yes Details →
2.2.18 26 Apr 2011 H1 M3 — Yes Details →
2.2.17 19 Apr 2011 H1 M3 — Yes Details →
2.2.16 16 Apr 2011 H1 M3 — Yes Details →
2.2.15 26 Jan 2011 H1 M3 — Yes Details →
2.2.14 05 Jan 2011 H1 M4 — Yes Details →
2.2.13 23 Dec 2010 H1 M4 — Yes Details →
2.2.12 05 Dec 2010 H1 M4 — Yes Details →
2.2.11 30 Nov 2010 H1 M4 — Yes Details →
2.2.10 17 Nov 2010 H1 M4 — Yes Details →
2.2.9.1 15 Nov 2010 H1 M4 — Yes Details →
2.2.9 26 Oct 2010 H1 M4 — Yes Details →
2.2.7 07 Oct 2010 H1 M4 — Yes Details →
2.2.6.1 13 Sep 2010 H1 M4 — Yes Details →
2.2.6 11 Sep 2010 H1 M4 — Yes Details →
2.2.5.2 11 Sep 2010 H1 M4 — Yes Details →
2.2.5.1 11 Sep 2010 H1 M4 — Yes Details →
2.2.5 17 Jun 2010 H1 M4 — Yes Details →
2.2.4 12 Jun 2010 H1 M4 — Yes Details →
2.2.3 08 Jun 2010 H1 M4 — Yes Details →
2.2.2 07 Jun 2010 H1 M4 — Yes Details →
2.2.1 13 May 2010 H1 M4 — Yes Details →
2.2.0 11 Apr 2010 H1 M4 — Yes Details →
2.1.5.3 29 Mar 2010 H1 M4 — Yes Details →
2.1.5.2 28 Mar 2010 H1 M4 — Yes Details →
2.1.5.1 28 Mar 2010 H1 M4 — Yes Details →
2.1.5 28 Mar 2010 H1 M4 — Yes Details →
2.1.3 22 Feb 2010 H1 M4 — Yes Details →
2.1.2 28 Jan 2010 H1 M4 — Yes Details →
2.1.1 25 Jan 2010 H1 M4 — Yes Details →
2.1.0 25 Jan 2010 H1 M4 — Yes Details →
2.0.5 24 Jan 2010 H1 M4 — Yes Details →
2.0.3 23 Jan 2010 H1 M4 — Yes Details →
1.6.0 14 Jan 2010 H1 M4 — Yes Details →
1.5.4 14 Jan 2010 H1 M4 — Yes Details →
1.5.3 12 Jan 2010 H1 M4 — Yes Details →
1.5.2 08 Jan 2010 H1 M4 — Yes Details →
1.5.1 04 Jan 2010 H1 M4 — Yes Details →
1.5.0 03 Jan 2010 H1 M4 — Yes Details →
1.4.3 31 Dec 2009 H1 M4 — Yes Details →
1.4.2 28 Dec 2009 H1 M4 — Yes Details →
1.4.1 27 Dec 2009 H1 M4 — Yes Details →
1.4.0 27 Dec 2009 H1 M4 — Yes Details →
1.3.5 27 Dec 2009 H1 M4 — Yes Details →
1.3.4 17 Dec 2009 H1 M4 — Yes Details →
1.3.3 17 Dec 2009 H1 M4 — Yes Details →
1.3.2 17 Dec 2009 H1 M4 — Yes Details →
1.3.1 13 Dec 2009 H1 M4 — Yes Details →
1.3.0 23 Nov 2009 H1 M4 — Yes Details →
1.2.9 23 Nov 2009 H1 M4 — Yes Details →
1.2.8 22 Nov 2009 H1 M4 — Yes Details →
1.2.6 19 Nov 2009 H1 M4 — Yes Details →
1.2.5 13 Nov 2009 H1 M4 — Yes Details →
1.2.1 05 Nov 2009 H1 M4 — Yes Details →
1.1.0 03 Nov 2009 H1 M4 — Yes Details →
1.0.0 25 Oct 2009 H1 M4 — Yes Details →

All 97 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 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for mail

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-9097: mail CRLF Injection vulnerability in RubyGems mail 6.1 medium 2.5.5 24 Oct 2017
CVE-2026-63435: Mail Package Email Address Spoofing via Malformed RFC 2047 Encoded-Words 5.3 medium 2.9.1 02 Sep 2026
CVE-2012-2139: Mail Path Traversal vulnerability in RubyGems Mail N/A medium 2.4.4 24 Oct 2017
CVE-2011-0739: Mail Improper Input Validation vulnerability in Ruby Mail gem N/A medium 2.2.15 24 Oct 2017
CVE-2012-2140: Mail Improper Input Validation vulnerability in RubyGems Mail N/A high 2.4.3 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 mail

Is mail safe to use?

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

Vulert scores mail 82/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 mail affected?

No. 2.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 mail should I use?

2.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 mail have?

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

1 vulnerability was recorded for mail 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 mail 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 mail for upcoming vulnerabilities?

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