Vulnerability Database · RubyGems · Package report

mailcatcher: vulnerability history, versions and safety

Q: How do I monitor mailcatcher for upcoming vulnerabilities?

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

mailcatcher is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mailcatcher vulnerabilities

Vulert verdict on mailcatcher 0.11.0 i

Updated on 23 Oct 2026

Good news: 0.11.0, the version you would install today, has no known vulnerabilities.

Package health score 86/100

Security Minor issues
Maintenance Sustainable
Popularity Key ecosystem project
Community Moderate

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

Current release 0.11.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 6,782 i
OpenSSF scorecard 4/10 i
Last release 1 month 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for mailcatcher, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.11.0	02 Sep 2026	none	MIT	—	Details →
0.10.0	25 May 2024	none	MIT	—	Details →
0.10.0.alpha1	17 May 2024	none	MIT	—	Details →
0.9.1.beta2	04 Aug 2023	none	MIT	—	Details →
0.9.1.beta1	30 Jul 2023	none	MIT	—	Details →
0.9.0	29 Jul 2023	none	MIT	—	Details →
0.9.0.beta2	29 Jan 2023	none	MIT	—	Details →
0.9.0.beta1	04 Jul 2022	none	MIT	—	Details →
0.8.2	05 Mar 2022	none	MIT	—	Details →
0.8.1	27 Jul 2021	none	MIT	—	Details →
0.8.0	20 Jul 2021	none	MIT	—	Details →
0.8.0.beta4	17 Jul 2021	none	MIT	—	Details →
0.8.0.beta3	27 Apr 2021	none	MIT	—	Details →
0.8.0.beta2	03 Apr 2020	none	MIT	—	Details →
0.7.1	04 Mar 2019	none	MIT	—	Details →
0.7.0	27 Feb 2019	none	MIT	—	Details →
0.7.0.beta1	31 Jul 2017	none	MIT	—	Details →
0.6.5	09 Aug 2016	none	MIT	—	Details →
0.6.4	04 Feb 2016	none	MIT	—	Details →
0.6.3	18 Jan 2016	none	MIT	—	Details →
0.6.2	15 Dec 2015	none	MIT	—	Details →
0.6.1	03 Feb 2015	none	MIT	—	Details →
0.6.0	29 Jan 2015	none	MIT	—	Details →
0.6.0pre1	27 Jan 2015	none	MIT	—	Details →
0.5.12	30 May 2013	none	MIT	—	Details →
0.5.11	12 Mar 2013	none	MIT	—	Details →
0.5.10	30 Sep 2012	none	—	—	Details →
0.5.9	10 Sep 2012	none	—	—	Details →
0.5.8	17 Jul 2012	none	—	—	Details →
0.5.7.2	10 Jul 2012	none	—	—	Details →
0.5.7.1	19 Jun 2012	none	—	—	Details →
0.5.7	19 Jun 2012	none	—	—	Details →
0.5.6	22 Mar 2012	none	—	—	Details →
0.5.5	22 Dec 2011	none	—	—	Details →
0.5.4	04 Dec 2011	none	—	—	Details →
0.5.3	10 Oct 2011	none	—	—	Details →
0.5.2	09 Oct 2011	none	—	—	Details →
0.5.1	08 Jul 2011	none	—	—	Details →
0.5.0	07 Jul 2011	none	—	—	Details →
0.4.7	24 Jun 2011	none	—	—	Details →
0.4.6	23 Jun 2011	none	—	—	Details →
0.4.5	10 Jun 2011	none	—	—	Details →
0.4.4	10 Jun 2011	none	—	—	Details →
0.4.3	02 Jun 2011	none	—	—	Details →
0.4.1	01 Jun 2011	none	—	—	Details →
0.4.0	31 May 2011	none	—	—	Details →
0.3.2	29 May 2011	none	—	—	Details →
0.3.1	29 May 2011	none	—	—	Details →
0.3.0	27 May 2011	none	—	—	Details →
0.2.4	10 May 2011	none	—	—	Details →
0.2.3	04 Nov 2010	none	—	—	Details →
0.2.2	04 Nov 2010	none	—	—	Details →
0.2.0	27 Oct 2010	none	—	—	Details →
0.1.6	26 Oct 2010	none	—	—	Details →
0.1.3	25 Oct 2010	none	—	—	Details →
0.1.2	25 Oct 2010	none	—	—	Details →
0.1.1	25 Oct 2010	none	—	—	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for mailcatcher

No vulnerabilities match this view.

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 mailcatcher

Is mailcatcher safe to use?

Vulert has no vulnerabilities on record for mailcatcher in RubyGems at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is mailcatcher's Vulert package health score?

Vulert scores mailcatcher 86/100, which reads as healthy. 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 mailcatcher affected?

No. 0.11.0, 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 mailcatcher should I use?

0.11.0 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 mailcatcher have?

0 vulnerabilities are recorded for mailcatcher in the RubyGems ecosystem: 0 critical, 0 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 mailcatcher vulnerabilities disclosed?

0 vulnerabilities were recorded for mailcatcher in the last 12 months. 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 mailcatcher 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 mailcatcher for upcoming vulnerabilities?

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