# CVE-2025-47153: Memory corruption in trixie

> Inconsistent off_t size in 32-bit builds of libuv and Node.js causes out-of-bounds memory access, potentially leading to crashes or code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 May 2025
- **Updated:** 2 May 2025
- **Also known as:** DEBIAN-CVE-2025-47153, DLA-4152-1, GHSA-5pxx-cc47-2282, UBUNTU-CVE-2025-47153

## What is CVE-2025-47153?

CVE-2025-47153 is a medium-severity memory corruption vulnerability in Debian trixie, published on 1 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1102 (Reliance on Machine-Dependent Data Representation)

## Which versions are affected by CVE-2025-47153?


## How do I fix CVE-2025-47153?

Apply the vendor's patch.

## Is CVE-2025-47153 being exploited?

There is no known exploitation of CVE-2025-47153 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47153 and fix it if it is affected.

What it is: CVE-2025-47153 is a medium-severity memory corruption vulnerability in Debian trixie, published on 1 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47153 in the wild and no public exploit code.

Affected product: Debian trixie. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47153/ (Markdown: https://insights.sbomify.com/CVE-2025-47153/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47153
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47153
- OSV: https://osv.dev/vulnerability/CVE-2025-47153

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47153/
Summaries are generated and may contain mistakes; the official description above is the record.