VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

stream-json: vulnerability history, versions and safety

stream-json is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 56 releases, from Sep 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all stream-json vulnerabilities

Vulert verdict on stream-json 3.7.0 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.7.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 6.2 i
  • With no published fix 0 i
  • Depended on by 433 packages i
  • Stars 1,205 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 stream-json, 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
3.7.0 19 Sep 2026 none BSD-3-Clause — Details →
3.6.0 28 Aug 2026 M1 BSD-3-Clause Yes Details →
3.5.0 07 Jul 2026 M3 BSD-3-Clause Yes Details →
3.4.0 08 Jun 2026 M4 BSD-3-Clause Yes Details →
3.3.0 29 May 2026 M4 BSD-3-Clause Yes Details →
3.2.0 27 May 2026 M4 BSD-3-Clause Yes Details →
3.1.0 23 May 2026 M4 BSD-3-Clause Yes Details →
3.0.0 21 May 2026 M4 BSD-3-Clause Yes Details →
2.1.0 31 Mar 2026 M4 BSD-3-Clause Yes Details →
2.0.0 19 Mar 2026 M4 BSD-3-Clause Yes Details →
1.9.1 12 Nov 2024 M3 BSD-3-Clause Yes Details →
1.9.0 23 Oct 2024 M3 BSD-3-Clause Yes Details →
1.8.0 30 May 2023 M3 BSD-3-Clause Yes Details →
1.7.5 23 Nov 2022 M3 BSD-3-Clause Yes Details →
1.7.4 17 Feb 2022 M3 BSD-3-Clause Yes Details →
1.7.3 14 Sep 2021 M3 BSD-3-Clause Yes Details →
1.7.2 04 Jul 2021 M3 BSD-3-Clause Yes Details →
1.7.1 18 Aug 2020 M3 BSD-3-Clause Yes Details →
1.7.0 11 Jul 2020 M3 BSD-3-Clause Yes Details →
1.6.1 10 Jul 2020 M3 BSD-3-Clause Yes Details →
1.6.0 10 Jul 2020 M3 BSD-3-Clause Yes Details →
1.5.0 27 Apr 2020 M3 BSD-3-Clause Yes Details →
1.4.1 26 Apr 2020 M3 BSD-3-Clause Yes Details →
1.4.0 26 Apr 2020 M3 BSD-3-Clause Yes Details →
1.3.3 21 Jan 2020 M3 BSD-3-Clause Yes Details →
1.3.2 08 Jan 2020 M3 BSD-3-Clause Yes Details →
1.3.1 02 Sep 2019 M3 BSD-3-Clause Yes Details →
1.3.0 16 Jun 2019 M3 BSD-3-Clause Yes Details →
1.2.1 14 Mar 2019 M3 BSD-3-Clause Yes Details →
1.2.0 13 Mar 2019 M3 BSD-3-Clause Yes Details →
1.1.4 16 Dec 2018 M3 BSD-3-Clause Yes Details →
1.1.3 09 Oct 2018 M3 BSD-3-Clause Yes Details →
1.1.2 09 Oct 2018 M3 BSD-3-Clause Yes Details →
1.1.1 25 Jul 2018 M3 BSD-3-Clause Yes Details →
1.1.0 29 Jun 2018 M3 BSD-3-Clause Yes Details →
1.0.3 27 Jun 2018 M3 BSD-3-Clause Yes Details →
1.0.2 21 Jun 2018 M3 BSD-3-Clause Yes Details →
1.0.1 20 Jun 2018 M3 BSD-3-Clause Yes Details →
1.0.0 19 Jun 2018 M3 BSD-3-Clause Yes Details →
0.6.1 25 Apr 2018 M3 BSD-3-Clause Yes Details →
0.6.0 25 Apr 2018 M3 BSD-3-Clause Yes Details →
0.5.3 25 Apr 2018 M3 BSD-3-Clause Yes Details →
0.5.2 13 Jul 2017 M3 BSD-3-Clause Yes Details →
0.5.1 16 Jun 2017 M3 BSD-3-Clause Yes Details →
0.5.0 16 Jun 2017 M3 BSD-3-Clause Yes Details →
0.4.2 10 Apr 2016 M3 BSD-3-Clause Yes Details →
0.4.1 12 Mar 2016 M3 BSD-3-Clause Yes Details →
0.4.0 10 Jun 2015 M3 BSD-3-Clause Yes Details →
0.3.0 08 Jun 2015 M3 BSD-3-Clause Yes Details →
0.2.2 06 Jun 2015 M3 BSD-3-Clause Yes Details →
0.2.1 06 Jun 2015 M3 BSD-3-Clause Yes Details →
0.2.0 24 May 2015 M3 BSD-3-Clause Yes Details →
0.1.0 21 Jan 2015 M3 BSD-3-Clause Yes Details →
0.0.5 16 Aug 2013 M3 BSD-3-Clause Yes Details →
0.0.4 14 Aug 2013 M3 BSD-3-Clause Yes Details →
0.0.3 11 Aug 2013 M3 BSD-3-Clause Yes Details →
0.0.1 11 Aug 2013 M3 BSD-3-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for stream-json

The 3 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-104182: stream-json Denial of Service via Inefficient JSONC Comment Parsing 6.2 medium 3.6.0 05 Oct 2026
CVE-2026-114129: stream-json FlexAssembler nested-input denial of service 6.2 medium 3.7.0 22 Oct 2026
CVE-2026-104183: stream-json Prototype Pollution Vulnerability 5.1 medium 3.6.0 05 Oct 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 stream-json

Is stream-json safe to use?

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

Vulert scores stream-json 73/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 stream-json affected?

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

Which version of stream-json should I use?

3.7.0 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 stream-json have?

4 vulnerabilities are recorded for stream-json in the npm ecosystem: 0 critical, 0 high, 4 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 stream-json vulnerabilities disclosed?

4 vulnerabilities were recorded for stream-json in the last 12 months, and the oldest entry in this database dates to 03 Sep 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 stream-json 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 stream-json for upcoming vulnerabilities?

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