VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

nodejs: vulnerability history, versions and safety

nodejs is a package in the Alpine ecosystem. Vulert records 29 vulnerabilities for it across 3 releases, from Jan 2025 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
29 vulnerabilities recorded U29
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
19 in the last 12 months

Most recent disclosure 04 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nodejs vulnerabilities

Vulert verdict on nodejs i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 04 Aug 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 29 vulnerabilities on record across 1 year, 19 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 29 over 1 year · 19 in the last year i
  • Latest disclosure 04 Aug 2026 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i

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 holds for nodejs, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
22.13.1-r0 U4 Yes Details →
22.11.0-r1 U10 Yes Details →
22.11.0-r0 U10 Yes Details →

Newest 3 of 3 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 10
  • 2026 19

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

03 Vulnerabilities

Recorded vulnerabilities for nodejs

The 5 most severe of 29 vulnerabilities recorded for this package

Search all 29 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Node.js TLS Hostname Handling Vulnerability - CVE-2026-48618 7.7 high 22.23.0-r0 26 Jun 2026
Critical Node.js WebCrypto Vulnerability in Alpine Packages: Process Crash Risk 7.5 high 22.23.0-r0 26 Jun 2026
Memory Exhaustion Vulnerability in Node.js HTTP/2 Handling 7.5 high 22.23.2-r0 04 Aug 2026
Heap Use-After-Free Vulnerability in Node.js HTTP/2 - CVE-2026-56848 7.5 high 22.23.2-r0 04 Aug 2026
Node.js Filesystem Access Over-Granting Vulnerability - CVE-2026-58043 7.5 high 22.23.2-r0 30 Jul 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 nodejs

Is nodejs safe to use?

Vulert records 29 vulnerabilities for nodejs in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 29 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does nodejs have?

29 vulnerabilities are recorded for nodejs in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 29 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nodejs vulnerabilities disclosed?

19 vulnerabilities were recorded for nodejs in the last 12 months, and the oldest entry in this database dates to 21 Jan 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 nodejs 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 nodejs for upcoming vulnerabilities?

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