BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2025-47153High confidence

Debian trixie — Reliance on Machine-Dependent Data Representation

Debian · trixie

6.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`nodejs`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2025-47153 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: libuv: Out-of-Bounds Access Due to Inconsistent off_t Size in libuv and Node.js Build on i386

58 known not affected

The vendor explicitly states that these products are not affected by this CVE.

libuv-devel as a component of Red Hat Enterprise Linux 10
libuv-static as a component of Red Hat Enterprise Linux 10
libuv.src as a component of Red Hat Enterprise Linux 10
nodejs as a component of Red Hat Enterprise Linux 10
nodejs-devel as a component of Red Hat Enterprise Linux 10
nodejs-docs as a component of Red Hat Enterprise Linux 10
nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
nodejs-libs as a component of Red Hat Enterprise Linux 10
nodejs-npm as a component of Red Hat Enterprise Linux 10
nodejs22.src as a component of Red Hat Enterprise Linux 10
libuv as a component of Red Hat Enterprise Linux 8
libuv-devel as a component of Red Hat Enterprise Linux 8

Summary: A flaw was found in the build process of libuv and Node.js on 32-bit systems. This vulnerability allows out-of-bounds memory access via mismatched _FILE_OFFSET_BITS settings during compilation, where libuv is built with 64-bit file offsets and Node.js with 32-bit defaults.
Remediation: No remediation text is recorded.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2025-12810

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified

What, why and how

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.

What

Why

The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Reliance on Machine-Dependent Data Representation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: High: exploitation depends on specific conditions
Security boundary: Changed: exploitation can affect a different security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-1102 ↗
CWE-1102: Reliance on Machine-Dependent Data Representation. The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-1102

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-12810Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2025-0915Debian Linux (libuv und Node.js): Schwachstelle ermöglicht nicht spezifizierten Angriff

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Debian Linux bezüglich der Pakete libuv und Node.js ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4575 https://www.cve.org/CVERecord?id=CVE-2025-4575 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-46727 https://www.cve.org/CVERecord?id=CVE-2025-46727 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-2025-47153 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-2025-47910 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48514 https://www.cve.org/CVERecord?id=CVE-2025-48514 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-2025-47153 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47908 https://www.cve.org/CVERecord?id=CVE-2025-47908 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-2025-47910 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48514 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: nodejs_0.10.0~dfsg1-1_i386.deb ≤ nodejs_20.19.0+dfsg-2_i386.deb
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 1 May 2025 · Last source change 2 May 2025, 19:02 UTC · CWE-1102 · Reliance on Machine-Dependent Data Representation

CVE recordCVE.org · 5.1

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2025-12810

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-05-01CVE published

ENISA EUVD · EUVD-2025-12810↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Debian trixie — Reliance on Machine-Dependent Data Representation

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2025-12810

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.