VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

next-intl: vulnerability history, versions and safety

next-intl is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 95 releases, from Apr 2026 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 06 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all next-intl vulnerabilities

Vulert verdict on next-intl 4.14.9 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 4.14.9 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 06 May 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 122 packages i
  • Stars 4,382 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT 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 next-intl, 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.14.9 02 Oct 2026 none MIT — Details →
0.0.0-canary-1244f54 02 Oct 2026 M2 MIT Yes Details →
0.0.0-canary-4932295 02 Oct 2026 M2 MIT Yes Details →
4.14.8 29 Sep 2026 none MIT — Details →
4.14.7 24 Sep 2026 none MIT — Details →
4.14.6 21 Sep 2026 none MIT — Details →
0.0.0-canary-c88e873 21 Sep 2026 M2 MIT Yes Details →
4.14.5 14 Sep 2026 none MIT — Details →
4.14.4 11 Sep 2026 none MIT — Details →
4.14.3 10 Sep 2026 none MIT — Details →
4.14.2 01 Sep 2026 none MIT — Details →
4.14.1 28 Aug 2026 none MIT — Details →
4.14.0 27 Aug 2026 none MIT — Details →
0.0.0-canary-061f08c 27 Aug 2026 M2 MIT Yes Details →
0.0.0-canary-0f7ee4c 21 Aug 2026 M2 MIT Yes Details →
0.0.0-canary-0f4e882 17 Aug 2026 M2 MIT Yes Details →
0.0.0-canary-315d747 17 Aug 2026 M2 MIT Yes Details →
4.13.7 17 Aug 2026 none MIT — Details →
0.0.0-canary-ada417e 12 Aug 2026 M2 MIT Yes Details →
4.13.6 10 Aug 2026 none MIT — Details →
4.13.5 04 Aug 2026 none MIT — Details →
4.13.4 23 Jul 2026 none MIT — Details →
4.13.3 21 Jul 2026 none MIT — Details →
4.13.2 10 Jul 2026 none MIT — Details →
0.0.0-canary-9f1cde4 02 Jul 2026 M2 MIT Yes Details →
4.13.1 30 Jun 2026 none MIT — Details →
0.0.0-canary-b75afc6 23 Jun 2026 M2 MIT Yes Details →
0.0.0-canary-375b031 05 Jun 2026 M2 MIT Yes Details →
4.13.0 28 May 2026 none MIT — Details →
4.12.0 13 May 2026 none MIT — Details →
0.0.0-canary-1a95c34 13 May 2026 M2 MIT Yes Details →
0.0.0-canary-97f8970 13 May 2026 M2 MIT Yes Details →
0.0.0-canary-8de90a4 12 May 2026 M2 MIT Yes Details →
0.0.0-canary-212f26c 12 May 2026 M2 MIT Yes Details →
0.0.0-canary-784589e 11 May 2026 M2 MIT Yes Details →
4.11.2 11 May 2026 none MIT — Details →
0.0.0-canary-f5d21f8 11 May 2026 M2 MIT Yes Details →
0.0.0-canary-7ef1b03 11 May 2026 M2 MIT Yes Details →
4.11.1 08 May 2026 none MIT — Details →
0.0.0-canary-8f7782e 05 May 2026 M2 MIT Yes Details →
4.11.0 28 Apr 2026 none MIT — Details →
4.10.1 28 Apr 2026 none MIT — Details →
4.10.0 28 Apr 2026 none MIT — Details →
4.9.2 27 Apr 2026 none MIT — Details →
4.9.1 10 Apr 2026 M1 MIT Yes Details →
4.9.0 01 Apr 2026 M2 MIT Yes Details →
4.8.4 31 Mar 2026 M2 MIT Yes Details →
4.8.3 16 Feb 2026 M2 MIT Yes Details →
4.8.2 02 Feb 2026 M2 MIT Yes Details →
0.0.0-canary-6b9a772 02 Feb 2026 M2 MIT Yes Details →
4.8.1 30 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-76127ff 30 Jan 2026 M2 MIT Yes Details →
4.8.0 28 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-c22cb45 26 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-53bd552 26 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-50c3c01 21 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-dc800af 19 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-c1152a2 16 Jan 2026 M2 MIT Yes Details →
4.7.0 01 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-0303294 01 Jan 2026 M2 MIT Yes Details →
0.0.0-canary-9b08798 29 Dec 2025 M2 MIT Yes Details →
4.6.1 16 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-2593cbb 16 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-d0a5db5 16 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-342f2f9 16 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-0892789 16 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-82bfdcf 15 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-c4c3768 15 Dec 2025 M2 MIT Yes Details →
4.6.0 12 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-d43359c 12 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-1cc54ff 12 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-63b8301 12 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-d4f4cde 11 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-2b0b3fc 11 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-919a0e3 11 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-62e3004 11 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-658487e 11 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-1ef30f5 10 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-632693c 09 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-6876534 09 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-683476f 05 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-853114a 03 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-65289bd 03 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-fb5f78a 03 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-bcf7147 03 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-3ad9bf4 03 Dec 2025 M2 MIT Yes Details →
4.5.8 03 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-067b6e7 02 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-1ccdee0 02 Dec 2025 M2 MIT Yes Details →
0.0.0-canary-873c3af 02 Dec 2025 M2 MIT Yes Details →
4.5.7 01 Dec 2025 M2 MIT Yes Details →
4.5.6 27 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-94d7fae 27 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-ee70d3b 26 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-8d81357 25 Nov 2025 M2 MIT Yes Details →
4.5.5 19 Nov 2025 M2 MIT Yes Details →
4.5.4 19 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-0c55fd4 19 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-c36123a 19 Nov 2025 M2 MIT Yes Details →
0.0.0-canary-2b10e99 14 Nov 2025 M2 MIT Yes Details →
4.5.3 13 Nov 2025 M2 — Yes Details →
0.0.0-canary-8f1d542 13 Nov 2025 M2 — Yes Details →
4.5.2 12 Nov 2025 M2 — Yes Details →
0.0.0-canary-00e2a17 12 Nov 2025 M2 — Yes Details →
4.5.1 11 Nov 2025 M2 — Yes Details →
4.5.0 07 Nov 2025 M2 — Yes Details →
0.0.0-canary-75af761 07 Nov 2025 M2 — Yes Details →
0.0.0-canary-e7eb9dd 06 Nov 2025 M2 — Yes Details →
0.0.0-canary-2b3a9ce 05 Nov 2025 M2 — Yes Details →
4.4.0 22 Oct 2025 M2 — Yes Details →
0.0.0-canary-f0249be 15 Oct 2025 M2 — Yes Details →
4.3.12 09 Oct 2025 M2 — Yes Details →
4.3.11 07 Oct 2025 M2 — Yes Details →
4.3.10 07 Oct 2025 M2 — Yes Details →
4.3.9 15 Sep 2025 M2 — Yes Details →
4.3.8 12 Sep 2025 M2 — Yes Details →
4.3.7 09 Sep 2025 M2 — Yes Details →
4.3.6 04 Sep 2025 M2 — Yes Details →
4.3.5 21 Aug 2025 M2 — Yes Details →
4.3.4 02 Jul 2025 M2 — Yes Details →

The newest 120 of 504 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for next-intl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Open Redirect Vulnerability in next-intl Package 6.9 medium 4.9.1 10 Apr 2026
Prototype Pollution Vulnerability in next-intl Package 4.2 medium 4.9.2 06 May 2026

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 next-intl

Is next-intl safe to use?

Vulert records 2 vulnerabilities for next-intl in npm: 0 critical, 0 high, 2 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 next-intl's Vulert package health score?

Vulert scores next-intl 78/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 next-intl affected?

No. 4.14.9, 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 next-intl should I use?

4.14.9 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 next-intl have?

2 vulnerabilities are recorded for next-intl in the npm ecosystem: 0 critical, 0 high, 2 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 next-intl vulnerabilities disclosed?

2 vulnerabilities were recorded for next-intl in the last 12 months, and the oldest entry in this database dates to 10 Apr 2026. 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 next-intl 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 next-intl for upcoming vulnerabilities?

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