Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 21 Jan 2026 21:15:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Title | nodejs: Nodejs uninitialized memory exposure | |
| Weaknesses | CWE-497 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Wed, 21 Jan 2026 20:30:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Wed, 21 Jan 2026 05:45:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact. | |
| References |
| |
| Metrics |
cvssV3_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2026-01-20T20:41:55.591Z
Reserved: 2025-08-07T15:00:05.576Z
Link: CVE-2025-55131
No data.
Status : Received
Published: 2026-01-20T21:16:03.320
Modified: 2026-01-20T21:16:03.320
Link: CVE-2025-55131
OpenCVE Enrichment
Updated: 2026-01-21T20:18:57Z