Quick answers
- Is CVE-2025-62517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-62517 being exploited in the wild.
- How severe is CVE-2025-62517?
- Medium severity, with a CVSS score of 5.9, published 23 October 2025.
- Which products and versions are affected?
- rollbar (npm) SEMVER:introduced=0,fixed=2.26.5.
- Is there a fix for CVE-2025-62517?
- Yes. rollbar (npm): upgrade to 2.26.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-62517 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-62517?
- Check whether you run rollbar (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- rollbar (npm): upgrade to 2.26.5 or later
npm install rollbar@2.26.5
Technical details
The vulnerability is a prototype pollution flaw (CWE-1321) in the merge() function of the Rollbar JavaScript library. An attacker can exploit this by crafting untrusted input containing special properties (e.g., "__proto__" or "constructor.prototype") that get passed to rollbar.configure(). No authentication or user interaction is required; the attack vector is network-based with high attack complexity. The impact is limited to integrity violations through property poisoning rather than confidentiality or availability breaches. Patches are available in versions 2.26.5 and 3.0.0-beta5.
Affected products
- Rollbar rollbar <=2.26.4, >=3.0.0-alpha1 and <=3.0.0-beta4
Identifiers
- CVE-2025-62517
- GHSA-xcg2-9pp4-j82x
Timeline
- 2025-10-23: disclosed
- 2025-10-23: patched: Fixed in versions 2.26.5 and 3.0.0-beta5