Vulnerability in nodejs (DEBIAN-CVE-2026-58039)

Summary

Vulnerability in nodejs (DEBIAN-CVE-2026-58039). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 20.19.2+dfsg-1+deb13u3 or later.

Original description

The description as published by the source.

A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js 22.x, 24.x, and 26.x.

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 DEBIAN-CVE-2026-58039 has been found in nodejs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nodejs to 20.19.2+dfsg-1+deb13u3 or later.
If unsure, ask your IT team or search "nodejs DEBIAN-CVE-2026-58039" on the vendor's site.

DEBIAN-CVE-2026-58039 (nodejs)
Attack vector: local / no user interaction
Patched: 20.19.2+dfsg-1+deb13u3 — 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.

📍 Affected scope

Check the vendor advisory for the affected versions of nodejs.

🔥 Severity

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

🔧 How to fix

Update to 20.19.2+dfsg-1+deb13u3.

🛡️ 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 20.19.2+dfsg-1+deb13u3
```
ステージング環境で 20.19.2+dfsg-1+deb13u3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.19.2+dfsg-1+deb13u3"}]}]

Debian:14 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.19.0+dfsg+~cs24.13.3-1"}]}]

References

advisory security-tracker.debian.org