CVE-2025-57348 json
node-cube vulnerable to prototype pollution
published 2025-09-24 13 mo ago modified 2026-06-17 4 mo ago also GHSA-8v65-5fw5-23wj , EUVD-2025-31069
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
The node-cube package (prior to version 5.0.0) contains a vulnerability in its handling of prototype chain initialization, which could allow an attacker to inject properties into the prototype of built-in objects. This issue, categorized under CWE-1321, arises from improper validation of user-supplied input in the package's resource initialization process. Successful exploitation may lead to denial of service or arbitrary code execution in affected environments. The vulnerability affects versions up to and including 5.0.0-beta.19, and no official fix has been released to date.
Patch / fix
- node-cube node-cube 5.0.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | node-cube | <=5.0.0-beta.19 |
no fix listed |
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/node-cube/cube/issues/153
web, third-party-advisory
-
github.com
/VulnSageAgent/PoCs/tree/main/JavaScript/prototype-pollution/CVE-2025-57348
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-57348
advisory
-
github.com
/node-cube/cube
package
Sources
- CVE List CVE-2025-57348
- GitHub Advisory GHSA-8v65-5fw5-23wj
- NVD CVE-2025-57348
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.