VulnerabilityPublished 24 Sep 2025Updated 25 Sep 2025

CVE-2025-57348: Prototype Pollution

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 5.0.0 : update affected systems when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Conduct an immediate audit of all applications and services to identify usage of the node-cube package, including transitive dependencies. 2) Where possible, isolate or sandbox components using node-cube to limit the impact of prototype pollution. 3) Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads attempting prototype pollution attacks. 4) Implement strict input validation and sanitization on all user-supplied data that may interact with node-cube resource initialization. 5) Consider temporarily replacing node-cube with alternative, secure packages or earlier versions not affected by this vulnerability if feasible. 6) Monitor security advisories closely for an official patch or updates from the node-cube maintainers and plan for rapid deployment once available. 7) Enhance logging and monitoring to detect anomalous behavior indicative of exploitation attempts. 8) Educate development teams about prototype pollution risks and secure coding practices to prevent similar issues in future dependencies.

Description

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.

Impact

For European organizations, the impact of CVE-2025-57348 can be significant, especially for those relying on node-cube in their software stacks, including web services, cloud applications, and internal tools. Exploitation could lead to denial of service, disrupting business operations and causing downtime. More critically, the possibility of arbitrary code execution could allow attackers to execute malicious payloads, potentially leading to data breaches, lateral movement within networks, or persistent backdoors. This is particularly concerning for sectors with high regulatory requirements such as finance, healthcare, and critical infrastructure, where service availability and data integrity are paramount. Additionally, the lack of an official patch increases the window of exposure, forcing organizations to consider temporary mitigations or alternative packages. The medium CVSS score reflects a moderate risk, but the ease of exploitation (no privileges or user interaction required) elevates the threat level. European organizations with public-facing applications or those integrating third-party JavaScript packages should be vigilant, as exploitation could also affect customer trust and regulatory compliance under GDPR if personal data is compromised.

CWE-1321Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (opens in a new tab)
Variant weakness
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Implementation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
Architecture and Design
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
Implementation · Input Validation
When handling untrusted objects, validating using a schema can be used.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Oct 2025, 01:01 UTC

WeaknessesCWE-1321

Technical details

References

Community reviews

Related threats