What is CVE-2025-62517?

CVE-2025-62517 is a medium-severity security vulnerability in rollbar (npm), affecting versions <= 2.26.4. It is fixed in 2.26.5, 3.0.0-beta5.

How severe is CVE-2025-62517?

CVE-2025-62517 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of rollbar are affected by CVE-2025-62517?

rollbar (npm) versions <= 2.26.4 is affected.

Is there a fix for CVE-2025-62517?

Yes. CVE-2025-62517 is fixed in 2.26.5, 3.0.0-beta5. Upgrade to this version or later.

Is CVE-2025-62517 exploitable, and should I be worried?

Whether CVE-2025-62517 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.

What actually determines whether CVE-2025-62517 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-62517?

Upgrade: rollbar to 2.26.5 or later, rollbar to 3.0.0-beta5 or later.

CVE-2025-62517 in rollbar | Intelligent Application Security

Q: How severe is CVE-2025-62517?

CVE-2025-62517 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of rollbar are affected by CVE-2025-62517?

rollbar (npm) versions <= 2.26.4 is affected.

Q: Is there a fix for CVE-2025-62517?

Yes. CVE-2025-62517 is fixed in 2.26.5, 3.0.0-beta5. Upgrade to this version or later.

Q: Is CVE-2025-62517 exploitable, and should I be worried?

Whether CVE-2025-62517 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.

Q: What actually determines whether CVE-2025-62517 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.

Q: How do I fix CVE-2025-62517?

Upgrade: rollbar to 2.26.5 or later, rollbar to 3.0.0-beta5 or later.

Summary

Workarounds

Ensure that values passed to rollbar.configure() do not contain untrusted input.

References

Fixed in https://github.com/rollbar/rollbar.js/pull/1394 (2.26.x) and https://github.com/rollbar/rollbar.js/pull/1390 (3.x)

Impact

Prototype pollution vulnerability in merge(). If application code calls rollbar.configure() with untrusted input, prototype pollution is possible.

CVE-2025-62517 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.26.5, 3.0.0-beta5); upgrading removes the vulnerable code path.

Affected versions

rollbar (<= 2.26.4) rollbar (>= 3.0.0-alpha1, <= 3.0.0-beta4)

Security releases

rollbar → 2.26.5 (npm) rollbar → 3.0.0-beta5 (npm)

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.

See it in your environment

Remediation advice

Fixed in 2.26.5 and 3.0.0-beta5.

Frequently Asked Questions

What is CVE-2025-62517? CVE-2025-62517 is a medium-severity security vulnerability in rollbar (npm), affecting versions <= 2.26.4. It is fixed in 2.26.5, 3.0.0-beta5.
How severe is CVE-2025-62517? CVE-2025-62517 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of rollbar are affected by CVE-2025-62517? rollbar (npm) versions <= 2.26.4 is affected.
Is there a fix for CVE-2025-62517? Yes. CVE-2025-62517 is fixed in 2.26.5, 3.0.0-beta5. Upgrade to this version or later.
Is CVE-2025-62517 exploitable, and should I be worried? Whether CVE-2025-62517 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-62517 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-62517?
- Upgrade rollbar to 2.26.5 or later
- Upgrade rollbar to 3.0.0-beta5 or later

Other vulnerabilities in rollbar

CVE-2025-57325