VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

serverless: vulnerability history, versions and safety

serverless is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 31 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all serverless vulnerabilities

Vulert verdict on serverless 4.45.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.45.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 31 Dec 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 956 packages i
  • Stars 46,924 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard 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 serverless, 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.45.0 20 Oct 2026 none — — Details →
4.44.0 14 Oct 2026 none — — Details →
4.43.0 24 Sep 2026 none — — Details →
4.42.0 09 Sep 2026 none — — Details →
4.41.1 26 Aug 2026 none — — Details →
4.41.0 10 Aug 2026 none — — Details →
4.40.0 22 Jul 2026 none — — Details →
4.39.0 08 Jul 2026 none — — Details →
4.38.1 19 Jun 2026 none — — Details →
4.38.0 17 Jun 2026 none — — Details →
4.37.0 27 May 2026 none — — Details →
4.36.1 14 May 2026 none — — Details →
4.36.0 12 May 2026 none — — Details →
4.35.1 06 May 2026 none — — Details →
4.35.0 30 Apr 2026 none — — Details →
4.34.0 10 Apr 2026 none — — Details →
4.33.3 02 Apr 2026 none — — Details →
4.33.2 01 Apr 2026 none — — Details →
4.33.1 31 Mar 2026 none — — Details →
4.33.0 19 Feb 2026 none — — Details →
4.32.0 12 Feb 2026 none — — Details →
4.31.2 27 Jan 2026 none — — Details →
4.31.1 27 Jan 2026 none — — Details →
4.31.0 15 Jan 2026 none — — Details →
4.30.0 08 Jan 2026 none — — Details →
4.29.4 02 Jan 2026 none — — Details →
4.29.3 29 Dec 2025 none — — Details →
4.29.0 17 Dec 2025 H1 — Yes Details →
4.28.0 11 Dec 2025 none — — Details →
4.27.1 08 Dec 2025 none — — Details →
4.27.0 03 Dec 2025 none — — Details →
4.26.1 02 Dec 2025 none — — Details →
4.26.0 01 Dec 2025 none — — Details →
4.25.0 21 Nov 2025 none — — Details →
4.24.0 20 Nov 2025 none — — Details →
4.23.0 05 Nov 2025 none — — Details →
4.22.0 22 Oct 2025 none — — Details →
4.21.1 16 Oct 2025 none — — Details →
4.21.0 08 Oct 2025 none — — Details →
4.20.2 03 Oct 2025 none — — Details →
4.20.1 02 Oct 2025 none — — Details →
4.20.0 02 Oct 2025 none — — Details →
4.19.1 16 Sep 2025 none — — Details →
4.19.0 15 Sep 2025 none — — Details →
4.18.2 26 Aug 2025 none — — Details →
4.18.1 21 Aug 2025 none — — Details →
4.18.0 06 Aug 2025 none — — Details →
4.17.2 24 Jul 2025 none — — Details →
4.17.1 17 Jun 2025 none — — Details →
4.17.0 05 Jun 2025 none — — Details →
4.16.1 04 Jun 2025 none — — Details →
4.16.0 04 Jun 2025 none — — Details →
4.15.1 28 May 2025 none — — Details →
4.15.0 27 May 2025 none — — Details →
4.14.4 20 May 2025 none — — Details →
4.14.3 06 May 2025 none — — Details →
4.14.2 01 May 2025 none — — Details →
4.14.1 19 Apr 2025 none — — Details →
4.14.0 17 Apr 2025 none — — Details →
4.13.0 15 Apr 2025 none — — Details →
4.12.0 07 Apr 2025 none — — Details →
4.11.1 03 Apr 2025 none — — Details →
4.11.0 03 Apr 2025 none — — Details →
4.10.1 01 Apr 2025 none — — Details →
4.10.0 31 Mar 2025 none — — Details →
4.9.1 24 Mar 2025 none — — Details →
4.9.0 14 Mar 2025 none — — Details →
4.8.0 10 Mar 2025 none — — Details →
4.7.0 24 Feb 2025 none — — Details →
4.6.4 21 Feb 2025 none — — Details →
4.6.3 17 Feb 2025 none — — Details →
4.6.2 06 Feb 2025 none — — Details →
4.6.1 04 Feb 2025 none — — Details →
4.6.0 03 Feb 2025 none — — Details →
4.5.4 03 Feb 2025 none — — Details →
4.5.3 31 Jan 2025 none — — Details →
4.5.2 30 Jan 2025 none — — Details →
4.5.1 29 Jan 2025 none — — Details →
4.5.0 23 Jan 2025 none — — Details →
4.4.21 23 Jan 2025 none — — Details →
4.4.20 23 Jan 2025 none — — Details →
4.4.19 15 Jan 2025 none — — Details →
4.4.18 18 Dec 2024 none — — Details →
3.40.0 17 Dec 2024 none MIT — Details →
4.4.17 17 Dec 2024 none — — Details →
3.40.0-19128fad 17 Dec 2024 none MIT — Details →
3.39.0-20c25e25 17 Dec 2024 none MIT — Details →
3.39.0-8b960a2e 17 Dec 2024 none MIT — Details →
4.4.16 11 Dec 2024 none — — Details →
4.4.15 09 Dec 2024 none — — Details →
4.4.14 03 Dec 2024 none — — Details →
4.4.13 27 Nov 2024 none — — Details →
4.4.12 25 Nov 2024 none — — Details →
4.4.11 19 Nov 2024 none — — Details →
4.4.10 15 Nov 2024 none — — Details →
4.4.9 14 Nov 2024 none — — Details →
4.4.8 14 Nov 2024 none — — Details →
4.4.7 21 Oct 2024 none — — Details →
4.4.6 14 Oct 2024 none — — Details →
4.4.5 09 Oct 2024 none — — Details →
4.4.4 01 Oct 2024 none — — Details →
4.4.3 26 Sep 2024 none — — Details →
4.4.2 25 Sep 2024 none — — Details →
4.4.1 24 Sep 2024 none — — Details →
4.4.0 19 Sep 2024 none — — Details →
4.3.3 16 Sep 2024 none — — Details →
4.3.2 10 Sep 2024 none — — Details →
4.3.1 10 Sep 2024 none — — Details →
4.3.0 10 Sep 2024 none — — Details →
4.2.5 04 Sep 2024 none — — Details →
4.2.4 26 Aug 2024 none — — Details →
4.2.3 22 Aug 2024 none — — Details →
4.2.1 21 Aug 2024 none — — Details →
4.2.0 21 Aug 2024 none — — Details →
4.1.24 21 Aug 2024 none — — Details →
4.1.23 19 Aug 2024 none — — Details →
4.1.22 13 Aug 2024 none — — Details →
4.1.21 09 Aug 2024 none — — Details →
4.1.20 08 Aug 2024 none — — Details →
4.1.19 01 Aug 2024 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for serverless

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-69256: Command Injection Vulnerability in Serverless MCP Server's list-projects Tool 7.5 high 4.29.3 31 Dec 2025

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 serverless

Is serverless safe to use?

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

Vulert scores serverless 84/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 serverless affected?

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

How many vulnerabilities does serverless have?

1 vulnerability is recorded for serverless in the npm ecosystem: 0 critical, 1 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 serverless vulnerabilities disclosed?

1 vulnerability was recorded for serverless in the last 12 months, and the oldest entry in this database dates to 31 Dec 2025. 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 serverless 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 serverless for upcoming vulnerabilities?

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