VulnerabilityPublished 24 Sep 2025Updated 26 Sep 2025

CVE-2025-57325: Prototype Pollution

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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

To mitigate this vulnerability, European organizations should first identify all instances of the Rollbar package in their software stack, including direct and transitive dependencies. Until an official patch is released, consider the following specific actions: 1) Implement input validation and sanitization on all data passed to Rollbar's utility.set function to prevent malicious payloads from reaching the vulnerable code path. 2) Employ runtime application self-protection (RASP) or Web Application Firewall (WAF) rules to detect and block suspicious payloads indicative of prototype pollution attempts targeting Rollbar. 3) Isolate or sandbox components using Rollbar to limit the blast radius of potential DoS conditions. 4) Monitor application logs and Rollbar error reports for unusual patterns or spikes that may indicate exploitation attempts. 5) Engage with Rollbar's vendor or community to obtain updates or patches as soon as they become available and plan for prompt deployment. 6) Consider temporarily disabling or replacing Rollbar with alternative error tracking solutions if the risk and impact justify such measures. 7) Conduct security testing, including fuzzing and penetration testing focused on prototype pollution vectors, to validate the effectiveness of mitigations.

Description

rollbar is a package designed to effortlessly track and debug errors in JavaScript applications. This package includes advanced error tracking features and an intuitive interface to help you identify and fix issues more quickly. A Prototype Pollution vulnerability in the utility.set function of rollbar v2.26.4 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

Impact

For European organizations, this vulnerability poses a risk primarily to the availability of web applications and services that incorporate the vulnerable Rollbar package. Since Rollbar is commonly used in modern JavaScript applications, including single-page applications and server-side Node.js environments, exploitation could lead to application crashes or denial of service conditions, disrupting business operations. This can affect customer-facing services, internal tools, and monitoring systems that rely on Rollbar for error reporting. The disruption could lead to loss of revenue, damage to reputation, and increased operational costs due to incident response and recovery efforts. Additionally, organizations in regulated sectors such as finance, healthcare, and critical infrastructure may face compliance challenges if service availability is impacted. While the vulnerability does not directly compromise data confidentiality or integrity, the resulting service outages could indirectly affect data processing and availability commitments under regulations like GDPR. The lack of required authentication and user interaction increases the risk of automated exploitation attempts, potentially amplifying the impact on European organizations with internet-facing applications.

Summary

CVE-2025-57325 is a Prototype Pollution vulnerability identified in the 'utility.set' function of the Rollbar JavaScript package, specifically in versions 2.26.4 and earlier. Rollbar is widely used for error tracking and debugging in JavaScript applications, providing developers with real-time insights into application errors. Prototype Pollution vulnerabilities occur when an attacker is able to inject or modify properties on the Object.prototype, which is the base object from which all JavaScript objects inherit. By manipulating this prototype, an attacker can alter the behavior of all objects in the application, potentially leading to unexpected behavior or security issues. In this case, the vulnerability allows an attacker to supply a crafted payload that modifies Object.prototype properties via the utility.set function. The primary impact identified is a denial of service (DoS), which can cause the affected application to crash or become unresponsive. The CVSS score of 7.5 (high severity) reflects that the vulnerability can be exploited remotely over the network without authentication or user interaction, and it impacts availability but not confidentiality or integrity. Although no known exploits are currently reported in the wild, the vulnerability's nature and ease of exploitation make it a significant risk for applications relying on Rollbar for error tracking. No patches or fixes are currently linked, indicating that affected users should monitor for updates or consider temporary mitigations. The underlying weakness is classified under CWE-1321, which relates to improper handling of prototype pollution in JavaScript objects.

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, 00:33 UTC

WeaknessesCWE-1321

Technical details

References

Community reviews

Related threats