Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-55130 critical CVSS 9.1

Vulnerability in node-min (CVE-2025-55130)

Summary

Vulnerability in node-min (CVE-2025-55130). Confidential information can be exposed externally. Mitigation: upgrade to 20.20.0, 22.22.0, 24.13.0, 25.3.0 or later.

Original description

The description as published by the source.

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.
This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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 CVE-2025-55130 has been found in node-min.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade node-min to 20.20.0, 22.22.0, 24.13.0, 25.3.0 or later.
If unsure, ask your IT team or search "node-min CVE-2025-55130" on the vendor's site.

CVE-2025-55130 (node-min) — CWE-289 / CVSS v3 9.1
Attack vector: local / no user interaction
Patched: 20.20.0, 22.22.0, 24.13.0, 25.3.0 — 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 (CWE-289) exists in node-min.

📍 Affected scope

Check the vendor advisory for the affected versions of node-min.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 20.20.0, 22.22.0, 24.13.0, 25.3.0.

🛡️ 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 'node-min' . 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. 1
    Identify exposure identify 
    grep -r 'node-min' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で node-min を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade node-min to 20.20.0, 22.22.0, 24.13.0, 25.3.0

    ステージング環境で 20.20.0, 22.22.0, 24.13.0, 25.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami node-min
[{"type":"SEMVER","events":[{"introduced":"20.0.0"},{"fixed":"20.20.0"},{"introduced":"21.0.0"},{"fixed":"22.22.0"},{"introduced":"23.0.0"},{"fixed":"24.13.0"},{"introduced":"25.0.0"},{"fixed":"25.3.0"}]}]
Bitnami node
[{"type":"SEMVER","events":[{"introduced":"20.0.0"},{"fixed":"20.20.0"},{"introduced":"21.0.0"},{"fixed":"22.22.0"},{"introduced":"23.0.0"},{"fixed":"24.13.0"},{"introduced":"25.0.0"},{"fixed":"25.3.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details