Vulnerability Database · RubyGems · Package report
mime-types-data: vulnerability history, versions and safety
mime-types-data is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the RubyGems ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on mime-types-data 3.2026.1020 i
Updated on 23 Oct 2026
Good news: 3.2026.1020, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Quiet
What to do: Stay on 3.2026.1020 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.2026.1020 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 3.2026.1020 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 46 i
- OpenSSF scorecard 5/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 mime-types-data, 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.
- 3.2026.1020 21 Oct 2026
- 3.2026.1013 17 Oct 2026
- 3.2026.1006 07 Oct 2026
- 3.2026.0929 30 Sep 2026
- 3.2026.0922 22 Sep 2026
- 3.2026.0921 21 Sep 2026
- 3.2026.0701 01 Jul 2026
- 3.2026.0414 14 Apr 2026
- 3.2026.0407 07 Apr 2026
- 3.2026.0331 31 Mar 2026
- 3.2026.0317 17 Mar 2026
- 3.2026.0303 03 Mar 2026
- 3.2026.0224 24 Feb 2026
- 3.2026.0203 03 Feb 2026
- 3.2026.0127 27 Jan 2026
- 3.2026.0113 13 Jan 2026
- 3.2025.0924 24 Sep 2025
- 3.2025.0916 17 Sep 2025
- 3.2025.0909 09 Sep 2025
- 3.2025.0902 03 Sep 2025
- 3.2025.0826 26 Aug 2025
- 3.2025.0819 19 Aug 2025
- 3.2025.0812 12 Aug 2025
- 3.2025.0805 06 Aug 2025
- 3.2025.0729 29 Jul 2025
- 3.2025.0722 23 Jul 2025
- 3.2025.0715 17 Jul 2025
- 3.2025.0708 08 Jul 2025
- 3.2025.0701 01 Jul 2025
- 3.2025.0624 24 Jun 2025
- 3.2025.0617 17 Jun 2025
- 3.2025.0610 12 Jun 2025
- 3.2025.0603 03 Jun 2025
- 3.2025.0527 27 May 2025
- 3.2025.0520 20 May 2025
- 3.2025.0514 14 May 2025
- 3.2025.0507 07 May 2025
- 3.2025.0507.pre1 07 May 2025
- 3.2025.0506 06 May 2025
- 3.2025.0429 29 Apr 2025
- 3.2025.0422 22 Apr 2025
- 3.2025.0415 15 Apr 2025
- 3.2025.0506.pre3 09 Apr 2025
- 3.2025.0408 08 Apr 2025
- 3.2025.0506.pre2 07 Apr 2025
- 3.2025.0506.pre1 04 Apr 2025
- 3.2025.0402 02 Apr 2025
- 3.2025.0325 25 Mar 2025
- 3.2025.0318 19 Mar 2025
- 3.2025.0304 04 Mar 2025
- 3.2025.0220 20 Feb 2025
- 3.2025.0204 05 Feb 2025
- 3.2025.0107 08 Jan 2025
- 3.2024.1203 03 Dec 2024
- 3.2024.1105 06 Nov 2024
- 3.2024.1001 02 Oct 2024
- 3.2024.0903 03 Sep 2024
- 3.2024.0820 20 Aug 2024
- 3.2024.0806 06 Aug 2024
- 3.2024.0702 02 Jul 2024
- 3.2024.0604 06 Jun 2024
- 3.2024.0507 07 May 2024
- 3.2024.0305 05 Mar 2024
- 3.2024.0206 06 Feb 2024
- 3.2023.1205 05 Dec 2023
- 3.2023.1003 03 Oct 2023
- 3.2023.0808 08 Aug 2023
- 3.2023.0218.1 18 Feb 2023
- 3.2023.0218 18 Feb 2023
- 3.2022.0105 06 Jan 2022
- 3.2021.1115 15 Nov 2021
- 3.2021.0901 02 Sep 2021
- 3.2021.0704 05 Jul 2021
- 3.2021.0225 26 Feb 2021
- 3.2021.0212 12 Feb 2021
- 3.2020.1104 05 Nov 2020
- 3.2020.0512 13 May 2020
- 3.2020.0425 26 Apr 2020
- 3.2019.1009 09 Oct 2019
- 3.2019.0904 05 Sep 2019
- 3.2019.0331 31 Mar 2019
- 3.2018.0812 12 Aug 2018
- 3.2016.0521 22 May 2016
- 3.2016.0221 22 Feb 2016
- 3.2015.1120 20 Nov 2015
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 3.2026.1020 | 21 Oct 2026 | none | MIT | — | Details → |
| 3.2026.1013 | 17 Oct 2026 | none | MIT | — | Details → |
| 3.2026.1006 | 07 Oct 2026 | none | MIT | — | Details → |
| 3.2026.0929 | 30 Sep 2026 | none | MIT | — | Details → |
| 3.2026.0922 | 22 Sep 2026 | none | MIT | — | Details → |
| 3.2026.0921 | 21 Sep 2026 | none | MIT | — | Details → |
| 3.2026.0701 | 01 Jul 2026 | none | MIT | — | Details → |
| 3.2026.0414 | 14 Apr 2026 | none | MIT | — | Details → |
| 3.2026.0407 | 07 Apr 2026 | none | MIT | — | Details → |
| 3.2026.0331 | 31 Mar 2026 | none | MIT | — | Details → |
| 3.2026.0317 | 17 Mar 2026 | none | MIT | — | Details → |
| 3.2026.0303 | 03 Mar 2026 | none | MIT | — | Details → |
| 3.2026.0224 | 24 Feb 2026 | none | MIT | — | Details → |
| 3.2026.0203 | 03 Feb 2026 | none | MIT | — | Details → |
| 3.2026.0127 | 27 Jan 2026 | none | MIT | — | Details → |
| 3.2026.0113 | 13 Jan 2026 | none | MIT | — | Details → |
| 3.2025.0924 | 24 Sep 2025 | none | MIT | — | Details → |
| 3.2025.0916 | 17 Sep 2025 | none | MIT | — | Details → |
| 3.2025.0909 | 09 Sep 2025 | none | MIT | — | Details → |
| 3.2025.0902 | 03 Sep 2025 | none | MIT | — | Details → |
| 3.2025.0826 | 26 Aug 2025 | none | MIT | — | Details → |
| 3.2025.0819 | 19 Aug 2025 | none | MIT | — | Details → |
| 3.2025.0812 | 12 Aug 2025 | none | MIT | — | Details → |
| 3.2025.0805 | 06 Aug 2025 | none | MIT | — | Details → |
| 3.2025.0729 | 29 Jul 2025 | none | MIT | — | Details → |
| 3.2025.0722 | 23 Jul 2025 | none | MIT | — | Details → |
| 3.2025.0715 | 17 Jul 2025 | none | MIT | — | Details → |
| 3.2025.0708 | 08 Jul 2025 | none | MIT | — | Details → |
| 3.2025.0701 | 01 Jul 2025 | none | MIT | — | Details → |
| 3.2025.0624 | 24 Jun 2025 | none | MIT | — | Details → |
| 3.2025.0617 | 17 Jun 2025 | none | MIT | — | Details → |
| 3.2025.0610 | 12 Jun 2025 | none | MIT | — | Details → |
| 3.2025.0603 | 03 Jun 2025 | none | MIT | — | Details → |
| 3.2025.0527 | 27 May 2025 | none | MIT | — | Details → |
| 3.2025.0520 | 20 May 2025 | none | MIT | — | Details → |
| 3.2025.0514 | 14 May 2025 | none | MIT | — | Details → |
| 3.2025.0507 | 07 May 2025 | none | MIT | — | Details → |
| 3.2025.0507.pre1 | 07 May 2025 | none | MIT | — | Details → |
| 3.2025.0506 | 06 May 2025 | none | MIT | — | Details → |
| 3.2025.0429 | 29 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0422 | 22 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0415 | 15 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0506.pre3 | 09 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0408 | 08 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0506.pre2 | 07 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0506.pre1 | 04 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0402 | 02 Apr 2025 | none | MIT | — | Details → |
| 3.2025.0325 | 25 Mar 2025 | none | MIT | — | Details → |
| 3.2025.0318 | 19 Mar 2025 | none | MIT | — | Details → |
| 3.2025.0304 | 04 Mar 2025 | none | MIT | — | Details → |
| 3.2025.0220 | 20 Feb 2025 | none | MIT | — | Details → |
| 3.2025.0204 | 05 Feb 2025 | none | MIT | — | Details → |
| 3.2025.0107 | 08 Jan 2025 | none | MIT | — | Details → |
| 3.2024.1203 | 03 Dec 2024 | none | MIT | — | Details → |
| 3.2024.1105 | 06 Nov 2024 | none | MIT | — | Details → |
| 3.2024.1001 | 02 Oct 2024 | none | MIT | — | Details → |
| 3.2024.0903 | 03 Sep 2024 | none | MIT | — | Details → |
| 3.2024.0820 | 20 Aug 2024 | none | MIT | — | Details → |
| 3.2024.0806 | 06 Aug 2024 | none | MIT | — | Details → |
| 3.2024.0702 | 02 Jul 2024 | none | MIT | — | Details → |
| 3.2024.0604 | 06 Jun 2024 | none | MIT | — | Details → |
| 3.2024.0507 | 07 May 2024 | none | MIT | — | Details → |
| 3.2024.0305 | 05 Mar 2024 | none | MIT | — | Details → |
| 3.2024.0206 | 06 Feb 2024 | none | MIT | — | Details → |
| 3.2023.1205 | 05 Dec 2023 | none | MIT | — | Details → |
| 3.2023.1003 | 03 Oct 2023 | none | MIT | — | Details → |
| 3.2023.0808 | 08 Aug 2023 | none | MIT | — | Details → |
| 3.2023.0218.1 | 18 Feb 2023 | none | MIT | — | Details → |
| 3.2023.0218 | 18 Feb 2023 | none | MIT | — | Details → |
| 3.2022.0105 | 06 Jan 2022 | none | MIT | — | Details → |
| 3.2021.1115 | 15 Nov 2021 | none | MIT | — | Details → |
| 3.2021.0901 | 02 Sep 2021 | none | MIT | — | Details → |
| 3.2021.0704 | 05 Jul 2021 | none | MIT | — | Details → |
| 3.2021.0225 | 26 Feb 2021 | none | MIT | — | Details → |
| 3.2021.0212 | 12 Feb 2021 | none | MIT | — | Details → |
| 3.2020.1104 | 05 Nov 2020 | none | MIT | — | Details → |
| 3.2020.0512 | 13 May 2020 | none | MIT | — | Details → |
| 3.2020.0425 | 26 Apr 2020 | none | MIT | — | Details → |
| 3.2019.1009 | 09 Oct 2019 | none | MIT | — | Details → |
| 3.2019.0904 | 05 Sep 2019 | none | MIT | — | Details → |
| 3.2019.0331 | 31 Mar 2019 | none | MIT | — | Details → |
| 3.2018.0812 | 12 Aug 2018 | none | MIT | — | Details → |
| 3.2016.0521 | 22 May 2016 | none | MIT | — | Details → |
| 3.2016.0221 | 22 Feb 2016 | none | MIT | — | Details → |
| 3.2015.1120 | 20 Nov 2015 | none | MIT | — | Details → |
All 85 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.
03 Vulnerabilities
Recorded vulnerabilities for mime-types-data
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
Questions
About mime-types-data
Is mime-types-data safe to use?
Vulert has no vulnerabilities on record for mime-types-data 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 mime-types-data's Vulert package health score?
Vulert scores mime-types-data 72/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 mime-types-data affected?
No. 3.2026.1020, 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 mime-types-data have?
0 vulnerabilities are recorded for mime-types-data 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 mime-types-data vulnerabilities disclosed?
0 vulnerabilities were recorded for mime-types-data 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 mime-types-data 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 mime-types-data for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mime-types-data version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.