Bug 2431350 (CVE-2025-55131)
| Summary: | CVE-2025-55131 nodejs: Nodejs uninitialized memory exposure | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | caswilli, kaycoth |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A memory exposure flaw has been discovered in Node.js. 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2431479, 2431481, 2431485, 2431488, 2431491, 2431495, 2431498 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2026-01-20 21:03:10 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:1843 https://access.redhat.com/errata/RHSA-2026:1843 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:1842 https://access.redhat.com/errata/RHSA-2026:1842 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:2422 https://access.redhat.com/errata/RHSA-2026:2422 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:2421 https://access.redhat.com/errata/RHSA-2026:2421 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:2420 https://access.redhat.com/errata/RHSA-2026:2420 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:2767 https://access.redhat.com/errata/RHSA-2026:2767 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2026:2768 https://access.redhat.com/errata/RHSA-2026:2768 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:2781 https://access.redhat.com/errata/RHSA-2026:2781 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:2783 https://access.redhat.com/errata/RHSA-2026:2783 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:2782 https://access.redhat.com/errata/RHSA-2026:2782 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:2864 https://access.redhat.com/errata/RHSA-2026:2864 This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:2899 https://access.redhat.com/errata/RHSA-2026:2899 |