Prototype pollution via unsanitized dependency names
Published Sep 24, 2025 · Updated Sep 24, 2025
Prototype pollution in node-cube through 5.0.0-beta.19 allows remote attackers to modify built-in object prototypes via crafted dependency input. The cycle_check setRequires method accepts proto as a dependency name and writes the resource name through that inherited key, changing Object.prototype. Exposure requires a consuming application to pass attacker-controlled dependency data into setRequires; the demonstrated consequence is process-wide property injection, while crashes or code execution depend on later use of polluted properties.
Summary
What happened
Prototype pollution in node-cube through 5.0.0-beta.19 allows remote attackers to modify built-in object prototypes via crafted dependency input. The cycle_check setRequires method accepts proto as a dependency name and writes the resource name through that inherited key, changing Object.prototype. Exposure requires a consuming application to pass attacker-controlled dependency data into setRequires; the demonstrated consequence is process-wide property injection, while crashes or code execution depend on later use of polluted properties.
The record
- CVE
- CVE-2025-57348
- Published
- Sep 24, 2025
- Updated
- Sep 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OrangeShieldInfos node-cube prototype-pollution PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo