Vulnerability in nodejs (ALPINE-CVE-2025-59465)

Summary

Vulnerability in nodejs (ALPINE-CVE-2025-59465). Risk of unauthorized operations or information disclosure. Exploitable via HPACK. Mitigation: upgrade to 22.22.2-r0 or later.

Original description

The description as published by the source.

A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash by triggering an unhandled TLSSocket error ECONNRESET. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
  socket.on('error', err => {
    console.log(err)
  })
})

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as ALPINE-CVE-2025-59465 has been found in nodejs.
Attackers can target a specific entry point like HPACK over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nodejs to 22.22.2-r0 or later.
If unsure, ask your IT team or search "nodejs ALPINE-CVE-2025-59465" on the vendor's site.

ALPINE-CVE-2025-59465 (nodejs)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: HPACK / TLSSocket / ECONNRESET
Patched: 22.22.2-r0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in nodejs. Attackers reach the vulnerable code path via HPACK without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of nodejs. Attack surface: HPACK / TLSSocket / ECONNRESET.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 22.22.2-r0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nodejs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'nodejs' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nodejs を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade nodejs to 22.22.2-r0
```
ステージング環境で 22.22.2-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Alpine:v3.21 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.22.2-r0"}]}]

Alpine:v3.22 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.22.0-r0"}]}]

References

advisory security.alpinelinux.org