VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

immer: vulnerability history, versions and safety

immer is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 29 releases, from Jan 2021 to Sep 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H2
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 immer vulnerabilities

Vulert verdict on immer 11.2.9 i

Updated on 23 Oct 2026

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

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

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

  • Current release 11.2.9 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 07 Sep 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 28,988 i
  • OpenSSF scorecard 5/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 immer, 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
11.2.9 22 Oct 2026 none MIT — Details →
11.2.8 22 Oct 2026 none MIT — Details →
11.2.7 21 Oct 2026 none MIT — Details →
11.2.6 21 Oct 2026 none MIT — Details →
11.2.5 21 Oct 2026 none MIT — Details →
11.2.4 21 Oct 2026 none MIT — Details →
11.2.3 20 Oct 2026 none MIT — Details →
11.2.2 20 Oct 2026 none MIT — Details →
11.2.1 20 Oct 2026 none MIT — Details →
11.2.0 20 Oct 2026 none MIT — Details →
11.1.23 20 Oct 2026 none MIT — Details →
11.1.22 20 Oct 2026 none MIT — Details →
11.1.21 02 Oct 2026 none MIT — Details →
11.1.20 02 Oct 2026 none MIT — Details →
11.1.19 02 Oct 2026 none MIT — Details →
11.1.18 19 Aug 2026 none MIT — Details →
11.1.17 16 Aug 2026 none MIT — Details →
11.1.16 05 Aug 2026 none MIT — Details →
11.1.15 16 Jul 2026 none MIT — Details →
11.1.14 16 Jul 2026 none MIT — Details →
11.1.13 16 Jul 2026 none MIT — Details →
11.1.12 16 Jul 2026 none MIT — Details →
11.1.11 03 Jul 2026 none MIT — Details →
11.1.10 03 Jul 2026 none MIT — Details →
11.1.9 01 Jul 2026 none MIT — Details →
11.1.8 08 May 2026 none MIT — Details →
11.1.7 06 May 2026 none MIT — Details →
11.1.6 04 May 2026 none MIT — Details →
11.1.5 04 May 2026 none MIT — Details →
11.1.4 10 Feb 2026 none MIT — Details →
11.1.3 29 Dec 2025 none MIT — Details →
11.1.2 29 Dec 2025 none MIT — Details →
11.1.0 20 Dec 2025 none MIT — Details →
11.0.1 28 Nov 2025 none MIT — Details →
11.0.0 23 Nov 2025 none MIT — Details →
10.2.0 25 Oct 2025 none MIT — Details →
10.1.3 01 Sep 2025 none MIT — Details →
10.1.2 01 Sep 2025 none MIT — Details →
10.1.1 27 Apr 2024 none MIT — Details →
10.1.0 27 Apr 2024 none MIT — Details →
10.0.4-beta 11 Mar 2024 none MIT — Details →
10.0.4 09 Mar 2024 none MIT — Details →
10.0.3 02 Oct 2023 none MIT — Details →
10.0.3-beta 23 Sep 2023 none MIT — Details →
10.0.2 09 May 2023 none MIT — Details →
10.0.1 17 Apr 2023 none MIT — Details →
10.0.0 17 Apr 2023 none MIT — Details →
10.0.0-beta.7 16 Apr 2023 none MIT — Details →
10.0.0-beta.6 06 Apr 2023 none MIT — Details →
10.0.0-beta.4 03 Apr 2023 none MIT — Details →
10.0.0-beta.3 03 Apr 2023 none MIT — Details →
10.0.0-beta.2 03 Apr 2023 none MIT — Details →
10.0.0-beta.1 03 Apr 2023 none MIT — Details →
9.0.21 23 Mar 2023 none MIT — Details →
9.0.20 23 Mar 2023 none MIT — Details →
9.0.19 27 Jan 2023 none MIT — Details →
9.0.18 15 Jan 2023 none MIT — Details →
9.0.17 02 Jan 2023 none MIT — Details →
9.0.16 22 Oct 2022 none MIT — Details →
9.0.15 13 Jun 2022 none MIT — Details →
9.0.14 12 May 2022 none MIT — Details →
9.0.13 11 May 2022 none MIT — Details →
9.0.12 11 Jan 2022 none MIT — Details →
9.0.11 11 Jan 2022 none MIT — Details →
9.0.10 11 Jan 2022 none MIT — Details →
9.0.9 11 Jan 2022 none MIT — Details →
9.0.8 11 Jan 2022 none MIT — Details →
9.0.7 24 Nov 2021 none MIT — Details →
9.0.6 31 Aug 2021 none MIT — Details →
9.0.5 05 Jul 2021 C1 H1 MIT Yes Details →
9.0.4 05 Jul 2021 C1 H1 MIT Yes Details →
9.0.3 09 Jun 2021 C1 H1 MIT Yes Details →
9.0.2 25 Apr 2021 C1 H1 MIT Yes Details →
9.0.1 20 Mar 2021 C1 H1 MIT Yes Details →
9.0.0 19 Mar 2021 C1 H1 MIT Yes Details →
9.0.0-beta.1 19 Mar 2021 C1 H1 MIT Yes Details →
8.0.4 19 Mar 2021 C1 H1 MIT Yes Details →
9.0.0-beta.0 19 Mar 2021 C1 H1 MIT Yes Details →
8.0.3 18 Mar 2021 C1 H1 MIT Yes Details →
8.0.2 17 Mar 2021 C1 H1 MIT Yes Details →
8.0.1 20 Jan 2021 C1 H1 MIT Yes Details →
8.0.0 17 Nov 2020 C1 H2 MIT Yes Details →
7.0.15 17 Nov 2020 C1 H2 MIT Yes Details →
7.0.14 20 Oct 2020 C1 H2 MIT Yes Details →
7.0.13 20 Oct 2020 C1 H2 MIT Yes Details →
7.0.12 20 Oct 2020 C1 H2 MIT Yes Details →
7.0.11 20 Oct 2020 C1 H2 MIT Yes Details →
7.0.10 20 Oct 2020 C1 H2 MIT Yes Details →
7.0.9 09 Sep 2020 C1 H2 MIT Yes Details →
7.0.8 25 Aug 2020 C1 H2 MIT Yes Details →
7.0.7 24 Jul 2020 C1 H2 MIT Yes Details →
7.0.6 24 Jul 2020 C1 H2 MIT Yes Details →
7.0.5 24 Jun 2020 C1 H2 MIT Yes Details →
7.0.4 22 Jun 2020 C1 H2 MIT Yes Details →
7.0.3 19 Jun 2020 C1 H2 MIT Yes Details →
7.0.2 19 Jun 2020 C1 H2 MIT Yes Details →
7.0.1 12 Jun 2020 C1 H2 MIT Yes Details →
7.0.0 10 Jun 2020 C1 H2 MIT Yes Details →
6.0.9 27 May 2020 none MIT — Details →
6.0.8 23 May 2020 none MIT — Details →
6.0.7 23 May 2020 none — — Details →
6.0.6 21 May 2020 none — — Details →
6.0.5 05 May 2020 none — — Details →
6.0.4 05 May 2020 none — — Details →
6.0.0-fix-425-2 31 Mar 2020 none — — Details →
6.0.0-fix-425 31 Mar 2020 none — — Details →
6.0.3 31 Mar 2020 none — — Details →
6.0.2 16 Mar 2020 none — — Details →
6.0.1 04 Mar 2020 none — — Details →
6.0.0 03 Mar 2020 none — — Details →
6.0.0-alpha.4 26 Feb 2020 none — — Details →
6.0.0-alpha.3 25 Feb 2020 none — — Details →
6.0.0-alpha.2 13 Feb 2020 none — — Details →
6.0.0-alpha.1 13 Feb 2020 none — — Details →
6.0.0-alpha.0 13 Feb 2020 none — — Details →
5.3.6 12 Feb 2020 none — — Details →
5.3.5 10 Feb 2020 none — — Details →
5.3.4 05 Feb 2020 none — — Details →
5.3.3 04 Feb 2020 none — — Details →
5.3.2 15 Jan 2020 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3

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

03 Vulnerabilities

Recorded vulnerabilities for immer

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-23436: Prototype Pollution in immer 9.8 critical 9.0.6 02 Sep 2021
CVE-2020-28477: Prototype Pollution in immer 7.5 high 8.0.1 20 Jan 2021
CVE-2021-3757: Prototype Pollution in immer 7.5 high 9.0.6 07 Sep 2021

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 immer

Is immer safe to use?

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

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

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

How many vulnerabilities does immer have?

3 vulnerabilities are recorded for immer in the npm ecosystem: 1 critical, 2 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 immer vulnerabilities disclosed?

0 vulnerabilities were recorded for immer in the last 12 months, and the oldest entry in this database dates to 20 Jan 2021. 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 immer 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 immer for upcoming vulnerabilities?

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