VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

stringstream: vulnerability history, versions and safety

stringstream is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 6 releases, from Jun 2019 to Jan 2022. 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
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 stringstream vulnerabilities

Vulert verdict on stringstream 1.0.0 i

Updated on 22 Oct 2026

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

Package health score 53/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 1.0.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 06 Jan 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 27 i
  • OpenSSF scorecard 1/10 i
  • Last release 97 months ago 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 stringstream, 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
1.0.0 23 Aug 2018 none MIT — Details →
0.0.6 17 May 2018 none MIT — Details →
0.0.5 25 Oct 2015 M2 MIT Yes Details →
0.0.4 21 Jan 2013 M2 MIT Yes Details →
0.0.3 27 Jun 2012 M2 non-standard Yes Details →
0.0.2 24 Jun 2012 M2 non-standard Yes Details →
0.0.1 23 Jun 2012 M2 non-standard Yes Details →
0.0.0 23 Jun 2012 M2 non-standard Yes Details →

All 8 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
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for stringstream

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Out-of-Bounds Read Vulnerability in Node.js stringstream 6.5 medium 0.0.6 06 Jan 2022
CVE-2018-21270: Out-of-bounds Read in stringstream N/A medium 0.0.6 20 Jun 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 stringstream

Is stringstream safe to use?

Vulert records 2 vulnerabilities for stringstream 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 stringstream's Vulert package health score?

Vulert scores stringstream 53/100, which reads as usable, but worth attention. 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 stringstream affected?

No. 1.0.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 stringstream should I use?

1.0.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 stringstream have?

2 vulnerabilities are recorded for stringstream 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 stringstream vulnerabilities disclosed?

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

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