Summary
rollbar vulnerable to prototype pollution
Workarounds
If application code directly imports set from rollbar/src/utility, ensure that the second argument does not receive untrusted input.
References
https://github.com/rollbar/rollbar.js/issues/1333#issuecomment-3353720946
Impact
Prototype pollution potential with the utility function rollbar/src/utility.set(). No impact when using the published public interface.
If application code directly imports set from rollbar/src/utility and then calls set with untrusted input in the second argument, it is vulnerable to prototype pollution.
POC:
const obj = {};
require("rollbar/src/utility").set(obj, "__proto__.polluted", "vulnerable");
console.log({}.polluted !== undefined ? '[POLLUTION_TRIGGERED]':'');
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed in version 2.26.5 and 3.0.0-beta5.
Frequently Asked Questions
- What is CVE-2025-57325? CVE-2025-57325 is a low-severity security vulnerability in rollbar (npm), affecting versions <= 2.26.4. It is fixed in 2.26.5, 3.0.0-beta5.
- Which versions of rollbar are affected by CVE-2025-57325? rollbar (npm) versions <= 2.26.4 is affected.
- Is there a fix for CVE-2025-57325? Yes. CVE-2025-57325 is fixed in 2.26.5, 3.0.0-beta5. Upgrade to this version or later.
- Is CVE-2025-57325 exploitable, and should I be worried? Whether CVE-2025-57325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-57325 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-57325?
- Upgrade
rollbarto 2.26.5 or later - Upgrade
rollbarto 3.0.0-beta5 or later
- Upgrade