VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

st: vulnerability history, versions and safety

st is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, from Aug 2018 to Aug 2020. 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 H1 M1
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 st vulnerabilities

Vulert verdict on st 4.0.12 i

Updated on 22 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.0.12 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 31 Aug 2020 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 380 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence ISC 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 st, 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.0.12 19 Oct 2026 none ISC — Details →
4.0.11 01 Oct 2026 none ISC — Details →
4.0.10 29 Aug 2026 none ISC — Details →
4.0.4 20 Jul 2026 none ISC — Details →
4.0.3 10 Jul 2026 none ISC — Details →
4.0.2 07 Jul 2026 none ISC — Details →
4.0.1 06 Jul 2026 none ISC — Details →
4.0.0 06 Jul 2026 none ISC — Details →
3.0.4 06 Jul 2026 none ISC — Details →
3.0.3 14 Aug 2025 none ISC — Details →
3.0.2 31 May 2025 none ISC — Details →
3.0.1 25 Oct 2024 none ISC — Details →
3.0.0 20 May 2021 none ISC — Details →
2.0.0 11 Nov 2019 none ISC — Details →
1.2.2 13 Oct 2017 none ISC — Details →
1.2.1 09 Oct 2017 M1 ISC Yes Details →
1.2.0 29 Jun 2016 M1 ISC Yes Details →
1.1.0 14 Dec 2015 M1 ISC Yes Details →
1.0.0 29 Sep 2015 M1 ISC Yes Details →
0.5.5 28 Jul 2015 M1 ISC Yes Details →
0.5.4 19 May 2015 M1 ISC Yes Details →
0.5.3 14 Feb 2015 M1 non-standard Yes Details →
0.5.2 25 Sep 2014 M1 non-standard Yes Details →
0.5.1 18 Jun 2014 M1 non-standard Yes Details →
0.5.0 13 Jun 2014 M1 non-standard Yes Details →
0.4.1 25 Mar 2014 M1 non-standard Yes Details →
0.4.0 24 Mar 2014 M1 non-standard Yes Details →
0.3.2 21 Mar 2014 M1 non-standard Yes Details →
0.3.1 18 Feb 2014 M1 non-standard Yes Details →
0.3.0 16 Feb 2014 M1 non-standard Yes Details →
0.2.6 10 Feb 2014 M1 non-standard Yes Details →
0.2.5 06 Feb 2014 M1 non-standard Yes Details →
0.2.4 04 Feb 2014 H1 M1 non-standard Yes Details →
0.2.3 18 Nov 2013 H1 M1 non-standard Yes Details →
0.2.2 18 Nov 2013 H1 M1 non-standard Yes Details →
0.2.1 20 Jun 2013 H1 M1 non-standard Yes Details →
0.2.0 18 Jun 2013 H1 M1 non-standard Yes Details →
0.1.4 29 May 2013 H1 M1 non-standard Yes Details →
0.1.3 06 Apr 2013 H1 M1 non-standard Yes Details →
0.1.2 10 Jan 2013 H1 M1 non-standard Yes Details →
0.1.1 06 Dec 2012 H1 M1 non-standard Yes Details →
0.1.0 16 Nov 2012 H1 M1 non-standard Yes Details →
0.0.12 08 Nov 2012 H1 M1 non-standard Yes Details →
0.0.11 26 Oct 2012 H1 M1 non-standard Yes Details →
0.0.10 22 Oct 2012 H1 M1 non-standard Yes Details →
0.0.9 16 Oct 2012 H1 M1 non-standard Yes Details →
0.0.8 16 Oct 2012 H1 M1 non-standard Yes Details →
0.0.7 20 Sep 2012 H1 M1 non-standard Yes Details →
0.0.6 17 Sep 2012 H1 M1 non-standard Yes Details →
0.0.5 21 Aug 2012 H1 M1 non-standard Yes Details →
0.0.4 11 Aug 2012 H1 M1 non-standard Yes Details →
0.0.3 11 Aug 2012 H1 M1 non-standard Yes Details →
0.0.2 11 Aug 2012 H1 M1 non-standard Yes Details →
0.0.1 10 Aug 2012 H1 M1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 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 st

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-3744: Directory Traversal in st 7.5 high 0.2.5 31 Aug 2020
CVE-2017-16224: Open Redirect in st 6.1 medium 1.2.2 06 Aug 2018

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 st

Is st safe to use?

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

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

No. 4.0.12, 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 st have?

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

0 vulnerabilities were recorded for st in the last 12 months, and the oldest entry in this database dates to 06 Aug 2018. 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 st 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 st for upcoming vulnerabilities?

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