VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

messageformat: vulnerability history, versions and safety

messageformat is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 39 releases, first recorded in Sep 2025. 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 L1
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 messageformat vulnerabilities

Vulert verdict on messageformat 4.1.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Sep 2025 i
  • Highest CVSS 1.7 i
  • With no published fix 0 i
  • Depended on by 68 packages i
  • Stars 1,772 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, 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 messageformat, 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
4.1.0 12 Oct 2026 none Apache-2.0 — Details →
4.0.0 25 Nov 2025 none Apache-2.0 — Details →
4.0.0-13 04 Sep 2025 none Apache-2.0 — Details →
4.0.0-12 14 May 2025 none Apache-2.0 — Details →
4.0.0-11 07 May 2025 none Apache-2.0 — Details →
4.0.0-10 24 Mar 2025 none Apache-2.0 — Details →
4.0.0-9 21 Nov 2024 none Apache-2.0 — Details →
4.0.0-8 02 Oct 2024 none Apache-2.0 — Details →
4.0.0-7 28 Feb 2024 none Apache-2.0 — Details →
4.0.0-6 07 Jan 2024 none Apache-2.0 — Details →
4.0.0-5 14 Nov 2023 none Apache-2.0 — Details →
4.0.0-4 08 Jun 2023 none Apache-2.0 — Details →
4.0.0-3.cf 14 Mar 2023 none Apache-2.0 — Details →
4.0.0-3 14 Mar 2023 none Apache-2.0 — Details →
4.0.0-2 08 Dec 2022 none Apache-2.0 — Details →
4.0.0-1 21 Oct 2022 none Apache-2.0 — Details →
4.0.0-0 16 Jul 2022 none Apache-2.0 — Details →
3.0.0-beta.2 12 Apr 2020 none MIT — Details →
3.0.0-beta.1 15 Oct 2019 none MIT — Details →
3.0.0-beta.0 15 Oct 2019 none MIT — Details →
2.3.0 17 Jul 2019 L1 MIT Yes Details →
2.2.1 18 May 2019 L1 MIT Yes Details →
2.2.0 02 May 2019 L1 MIT Yes Details →
2.1.0 03 Mar 2019 L1 MIT Yes Details →
2.0.5 15 Dec 2018 L1 MIT Yes Details →
2.0.4 21 Jul 2018 L1 MIT Yes Details →
2.0.3 19 Jul 2018 L1 MIT Yes Details →
2.0.2 23 Apr 2018 L1 MIT Yes Details →
2.0.1 18 Apr 2018 L1 MIT Yes Details →
2.0.0 04 Apr 2018 L1 MIT Yes Details →
2.0.0-beta.5 28 Mar 2018 L1 MIT Yes Details →
2.0.0-beta.4 23 Mar 2018 L1 MIT Yes Details →
2.0.0-beta.3 23 Mar 2018 L1 MIT Yes Details →
2.0.0-beta.2 17 Mar 2018 L1 MIT Yes Details →
2.0.0-beta.1 15 Mar 2018 L1 MIT Yes Details →
1.1.1 06 Jan 2018 L1 MIT Yes Details →
1.1.0 18 Nov 2017 L1 MIT Yes Details →
1.0.2 26 Sep 2016 L1 MIT Yes Details →
1.0.1 26 Sep 2016 L1 MIT Yes Details →
1.0.0 01 Sep 2016 L1 MIT Yes Details →
1.0.0-rc.3 04 Jul 2016 L1 MIT Yes Details →
1.0.0-rc.2 17 Apr 2016 L1 MIT Yes Details →
1.0.0-rc.1 17 Apr 2016 L1 MIT Yes Details →
0.3.1 20 Feb 2016 L1 MIT Yes Details →
0.3.0 30 Jan 2016 L1 MIT Yes Details →
0.3.0-1 06 Apr 2015 L1 non-standard Yes Details →
0.2.2 06 Apr 2015 L1 non-standard Yes Details →
0.3.0-0 17 Mar 2015 L1 non-standard Yes Details →
0.2.1 17 Sep 2014 L1 non-standard Yes Details →
0.2.0 30 Jul 2014 L1 non-standard Yes Details →
0.1.8 19 Feb 2014 L1 non-standard Yes Details →
0.1.7 28 Jan 2014 L1 non-standard Yes Details →
0.1.6 10 May 2013 L1 non-standard Yes Details →
0.1.5 15 Nov 2012 L1 non-standard Yes Details →
0.1.4 26 Jun 2012 L1 non-standard Yes Details →
0.1.3 26 Jun 2012 L1 non-standard Yes Details →
0.1.2 26 Jun 2012 L1 non-standard Yes Details →
0.1.1 03 Mar 2012 L1 non-standard Yes Details →
0.1.0 28 Feb 2012 L1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 messageformat

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-57349: Prototype Pollution Vulnerability in messageformat Package 1.7 low 3.0.0-beta.0 24 Sep 2025

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 messageformat

Is messageformat safe to use?

Vulert records 1 vulnerabilities for messageformat in npm: 0 critical, 0 high, 0 medium and 1 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 messageformat's Vulert package health score?

Vulert scores messageformat 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 messageformat affected?

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

How many vulnerabilities does messageformat have?

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

How often are new messageformat vulnerabilities disclosed?

0 vulnerabilities were recorded for messageformat in the last 12 months, and the oldest entry in this database dates to 24 Sep 2025. 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 messageformat 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 messageformat for upcoming vulnerabilities?

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