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.

The out-of-bounds access vulnerability allows attackers to potentially trigger a denial-of-service (DoS) condition or, in more complex scenarios, achieve arbitrary code execution. While the vulnerability isn't inherent to the Node.js software itself, a malicious actor could exploit it during the build or deployment process, particularly if they control the build environment or can inject malicious code into the build pipeline. The impact is amplified in environments where Node.js applications are built and deployed automatically, as this could allow attackers to compromise the entire system. This vulnerability is similar to other memory corruption issues that have been exploited to gain control of systems.

Organizations using Debian GNU/Linux with i386 architecture and relying on pre-built Node.js packages are particularly at risk. Developers who build Node.js from source on i386 systems are also potentially affected. Shared hosting environments that automatically build and deploy Node.js applications could be vulnerable if they use affected versions.

• linux / server:

journalctl -u nodejs | grep -i 'off_t size'

• linux / server:

ps aux | grep nodejs | grep -i 'i386'

• generic web: Inspect build server logs for errors related to off_t size or file access during Node.js builds on i386 systems.

1. 2025-05-01Disclosure

   disclosure

1. Gereserveerd2025-05-01
2. Gepubliceerd2025-05-01
3. Gewijzigd2025-05-02
4. EPSS bijgewerkt2026-03-23

The primary mitigation for CVE-2025-47153 is to upgrade Node.js to version 20.19.1 or later. If upgrading is not immediately feasible due to compatibility constraints or breaking changes, consider temporarily isolating affected systems and limiting network access. While a direct WAF rule is unlikely to be effective, monitoring build processes for unusual activity and ensuring the integrity of build dependencies can help detect potential exploitation attempts. Review build scripts and configurations for any suspicious modifications. After upgrading, confirm the fix by attempting to build Node.js on an i386 Debian system and verifying that the off_t size is handled consistently.