CVE-2025-47153

What it is

Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through nodejs_20.19.0+dfsg-2_i386.deb for Debian GNU/Linux, have an inconsistent off_t size (e.g., building on i386 Debian always uses _FILE_OFFSET_BITS=64 for the libuv dynamic library, but uses the _FILE_OFFSET_BITS global system default of 32 for nodejs), leading to out-of-bounds access. NOTE: this is not a problem in the Node.js software itself. In particular, the Node.js website's download page does not offer prebuilt Node.js for Linux on i386.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-05-01 07:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:27 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-05-01 07:15 UTC

Last modified

2026-06-17 09:27 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-1102

Record status

Deferred

Attack profile CVSS 3.1 · 6.5

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-47153.md and follow it. Check whether this project is affected by CVE-2025-47153. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge