VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

serialize-javascript: vulnerability history, versions and safety

serialize-javascript is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 30 releases, from Dec 2019 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M3 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 30 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all serialize-javascript vulnerabilities

Vulert verdict on serialize-javascript 7.1.3 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 7.1.3 — unaffected i
  • Vulnerabilities on record 6 over 6 years · 3 in the last year i
  • Latest disclosure 30 Sep 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 2,925 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 serialize-javascript, 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
7.1.3 22 Oct 2026 none BSD-3-Clause — Details →
7.1.2 23 Sep 2026 none BSD-3-Clause — Details →
7.1.1 29 Aug 2026 L1 BSD-3-Clause Yes Details →
7.1.0 08 Aug 2026 none BSD-3-Clause — Details →
7.0.7 30 Jun 2026 none BSD-3-Clause — Details →
7.0.6 17 Jun 2026 none BSD-3-Clause — Details →
7.0.5 25 Mar 2026 none BSD-3-Clause — Details →
7.0.4 02 Mar 2026 M1 BSD-3-Clause Yes Details →
7.0.3 27 Feb 2026 M1 BSD-3-Clause Yes Details →
7.0.2 07 Dec 2025 H1 M1 BSD-3-Clause Yes Details →
7.0.1 28 Nov 2025 H1 M1 BSD-3-Clause Yes Details →
7.0.0 04 Oct 2025 H1 M1 BSD-3-Clause Yes Details →
6.0.2 09 Jan 2024 H1 M1 BSD-3-Clause Yes Details →
6.0.1 15 Jan 2023 H1 M2 BSD-3-Clause Yes Details →
6.0.0 21 Jun 2021 H1 M2 BSD-3-Clause Yes Details →
5.0.1 10 Sep 2020 H1 M1 BSD-3-Clause Yes Details →
5.0.0 09 Sep 2020 H1 M1 BSD-3-Clause Yes Details →
4.0.0 08 Jun 2020 H1 M1 BSD-3-Clause Yes Details →
3.1.0 28 May 2020 H1 M1 BSD-3-Clause Yes Details →
3.0.0 16 Feb 2020 H2 M1 BSD-3-Clause Yes Details →
2.1.2 09 Dec 2019 H2 M1 BSD-3-Clause Yes Details →
2.1.1 05 Dec 2019 H2 M1 BSD-3-Clause Yes Details →
2.1.0 04 Sep 2019 H2 M2 BSD-3-Clause Yes Details →
2.0.0 04 Sep 2019 H2 M2 BSD-3-Clause Yes Details →
1.9.1 04 Sep 2019 H2 M2 BSD-3-Clause Yes Details →
1.9.0 29 Aug 2019 H2 M2 BSD-3-Clause Yes Details →
1.8.0 20 Aug 2019 H2 M2 BSD-3-Clause Yes Details →
1.7.0 16 Apr 2019 H2 M2 BSD-3-Clause Yes Details →
1.6.1 28 Dec 2018 H2 M2 BSD-3-Clause Yes Details →
1.6.0 24 Dec 2018 H2 M2 BSD-3-Clause Yes Details →
1.5.0 18 Apr 2018 H2 M2 BSD-3-Clause Yes Details →
1.4.0 15 Jul 2017 H2 M2 BSD-3-Clause Yes Details →
1.3.0 31 May 2016 H2 M2 BSD-3-Clause Yes Details →
1.2.0 29 Feb 2016 H2 M2 BSD-3-Clause Yes Details →
1.1.2 09 Sep 2015 H2 M2 BSD-3-Clause Yes Details →
1.0.0 16 Sep 2014 H2 M2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1
  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for serialize-javascript

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7660: Insecure serialization leading to RCE in serialize-javascript 8.1 high 3.1.0 11 Aug 2020
Remote Code Execution Vulnerability in serialize-javascript Package 8.1 high 7.0.3 28 Feb 2026
CVE-2026-34043: Denial of Service in serialize-javascript via Crafted Array-like Objects 5.9 medium 7.0.5 27 Mar 2026
CVE-2024-11831: Critical XSS Vulnerability in serialize-javascript Package 5.4 medium 6.0.2 10 Feb 2025
CVE-2019-16769: Cross-Site Scripting in serialize-javascript 4.2 medium 2.1.1 05 Dec 2019

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 serialize-javascript

Is serialize-javascript safe to use?

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

Vulert scores serialize-javascript 75/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 serialize-javascript affected?

No. 7.1.3, 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 serialize-javascript have?

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

3 vulnerabilities were recorded for serialize-javascript in the last 12 months, and the oldest entry in this database dates to 05 Dec 2019. 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 serialize-javascript 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 serialize-javascript for upcoming vulnerabilities?

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