VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

rollbar: vulnerability history, versions and safety

rollbar is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Sep 2025 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 L2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 23 Oct 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rollbar vulnerabilities

Vulert verdict on rollbar 4.1.0 i

Updated on 23 Oct 2026

Careful: 4.1.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.1.0 — affected i
  • Vulnerabilities on record 3 over 1 year · 1 in the last year i
  • Latest disclosure 23 Oct 2025 i
  • Highest CVSS 5.9 i
  • With no published fix 1 i
  • Depended on by 3 packages i
  • Stars 587 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for rollbar, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.1.0 18 Oct 2026 L1 MIT No Details →
4.0.0 06 Oct 2026 L1 MIT No Details →
3.1.0 12 Mar 2026 L1 MIT No Details →
3.0.0 27 Feb 2026 L1 MIT No Details →
3.0.0-rc.1 22 Oct 2025 L1 MIT No Details →
2.26.5 17 Oct 2025 L1 MIT No Details →
3.0.0-beta.5 17 Oct 2025 L1 MIT No Details →
3.0.0-beta.4 09 Oct 2025 L1 MIT No Details →
3.0.0-beta.3 19 Sep 2025 L1 MIT No Details →
3.0.0-beta.2 19 Sep 2025 L1 MIT No Details →
3.0.0-beta.1 18 Aug 2025 L1 MIT No Details →
3.0.0-alpha.6 08 Aug 2025 L1 MIT No Details →
3.0.0-alpha.5 05 Aug 2025 L1 MIT No Details →
3.0.0-alpha.4 24 Jul 2025 L1 MIT No Details →
3.0.0-alpha.3 18 Jul 2025 L1 MIT No Details →
3.0.0-alpha.2 26 Jun 2025 L1 MIT No Details →
3.0.0-alpha.1 13 Jun 2025 L1 MIT No Details →
2.26.4 19 Mar 2024 M1 L2 MIT No Details →
2.26.3 15 Feb 2024 M1 L2 MIT No Details →
2.26.2 29 Jun 2023 M1 L2 MIT No Details →
2.26.1 04 Jan 2023 M1 L2 MIT No Details →
2.26.0 30 Nov 2022 M1 L2 MIT No Details →
2.25.2 14 Sep 2022 M1 L2 MIT No Details →
2.25.1 01 Aug 2022 M1 L2 MIT No Details →
2.25.0 15 Apr 2022 M1 L2 MIT No Details →
2.24.1 16 Mar 2022 M1 L2 MIT No Details →
2.24.0 01 Jul 2021 M1 L2 MIT No Details →
2.23.0 24 Jun 2021 M1 L2 MIT No Details →
2.22.0 27 May 2021 M1 L2 MIT No Details →
2.21.1 17 Mar 2021 M1 L2 MIT No Details →
2.21.0 16 Feb 2021 M1 L2 MIT No Details →
2.20.0 29 Jan 2021 M1 L2 MIT No Details →
2.19.4 14 Oct 2020 M1 L2 MIT No Details →
2.19.3 24 Aug 2020 M1 L2 MIT No Details →
2.19.2 07 Aug 2020 M1 L2 MIT No Details →
2.19.1 30 Jul 2020 M1 L2 MIT No Details →
2.19.0 24 Jul 2020 M1 L2 MIT No Details →
2.18.0 07 Jul 2020 M1 L2 MIT No Details →
2.17.0 17 Jun 2020 M1 L2 MIT No Details →
2.16.2 18 May 2020 M1 L2 MIT No Details →
2.16.1 13 May 2020 M1 L2 MIT No Details →
2.16.0 13 May 2020 M1 L2 MIT No Details →
2.15.2 21 Apr 2020 M1 L2 MIT No Details →
2.15.1 14 Apr 2020 M1 L2 MIT No Details →
2.15.0 06 Mar 2020 M1 L2 MIT No Details →
2.14.4 12 Nov 2019 M1 L2 MIT No Details →
2.14.3 08 Nov 2019 M1 L2 MIT No Details →
2.14.2 06 Nov 2019 M1 L2 MIT No Details →
2.14.0 01 Nov 2019 M1 L2 MIT No Details →
2.13.0 12 Sep 2019 M1 L2 MIT No Details →
2.12.3 29 Aug 2019 M1 L2 MIT No Details →
2.12.2 22 Aug 2019 M1 L2 MIT No Details →
2.12.1 21 Aug 2019 M1 L2 MIT No Details →
2.12.0 15 Aug 2019 M1 L2 MIT No Details →
2.11.0 02 Aug 2019 M1 L2 MIT No Details →
2.10.0 31 Jul 2019 M1 L2 MIT No Details →
2.9.0 25 Jul 2019 M1 L2 MIT No Details →
2.8.1 06 Jul 2019 M1 L2 MIT No Details →
2.8.0 05 Jul 2019 M1 L2 MIT No Details →
2.7.1 22 May 2019 M1 L2 MIT No Details →
2.7.0 15 May 2019 M1 L2 MIT No Details →
2.6.1 25 Apr 2019 M1 L2 MIT No Details →
2.6.0 22 Apr 2019 M1 L2 MIT No Details →
2.5.5 08 Apr 2019 M1 L2 MIT No Details →
2.5.4 15 Mar 2019 M1 L2 MIT No Details →
2.5.3 04 Mar 2019 M1 L2 MIT No Details →
2.5.2 23 Jan 2019 M1 L2 MIT No Details →
2.5.1 27 Nov 2018 M1 L2 MIT No Details →
2.5.0 22 Oct 2018 M1 L2 MIT No Details →
2.4.7 20 Sep 2018 M1 L2 MIT No Details →
2.4.6 11 Sep 2018 M1 L2 MIT No Details →
2.4.5 28 Aug 2018 M1 L2 MIT No Details →
2.4.4 25 Jul 2018 M1 L2 MIT No Details →
2.4.3 25 Jul 2018 M1 L2 MIT No Details →
2.4.2 29 Jun 2018 M1 L2 MIT No Details →
2.4.1 31 May 2018 M1 L2 MIT No Details →
2.4.0 16 May 2018 M1 L2 MIT No Details →
2.3.9 17 Feb 2018 M1 L2 MIT No Details →
2.3.8 01 Feb 2018 M1 L2 MIT No Details →
2.3.7 12 Jan 2018 M1 L2 MIT No Details →
2.3.6 06 Jan 2018 M1 L2 MIT No Details →
2.3.5 05 Jan 2018 M1 L2 MIT No Details →
2.3.4 04 Jan 2018 M1 L2 MIT No Details →
2.3.3 13 Dec 2017 M1 L2 MIT No Details →
2.3.2 01 Dec 2017 M1 L2 MIT No Details →
2.3.1 02 Nov 2017 M1 L2 MIT No Details →
2.3.0 31 Oct 2017 M1 L2 MIT No Details →
2.2.10 17 Oct 2017 M1 L2 MIT No Details →
2.2.9 02 Oct 2017 M1 L2 MIT No Details →
2.2.8 19 Sep 2017 M1 L2 MIT No Details →
2.2.7 05 Sep 2017 M1 L2 MIT No Details →
2.2.6 27 Aug 2017 M1 L2 MIT No Details →
2.2.5 26 Aug 2017 M1 L2 MIT No Details →
2.2.4 26 Aug 2017 M1 L2 MIT No Details →
2.2.3 18 Aug 2017 M1 L2 MIT No Details →
2.2.2 18 Aug 2017 M1 L2 MIT No Details →
2.2.1 17 Aug 2017 M1 L2 MIT No Details →
2.2.0 15 Aug 2017 M1 L2 MIT No Details →
2.2.0-alpha.1 09 Aug 2017 M1 L2 MIT No Details →
2.1.3 07 Aug 2017 M1 L2 MIT No Details →
2.1.1 31 Jul 2017 M1 L2 — No Details →
2.1.0 03 Jul 2017 M1 L2 — No Details →
2.0.4 03 Jun 2017 M1 L2 — No Details →
2.0.3 01 Jun 2017 M1 L2 — No Details →
2.0.2 23 May 2017 M1 L2 — No Details →
2.0.1 19 May 2017 M1 L2 — No Details →
2.0.0 15 May 2017 M1 L2 — No Details →
2.0.0-beta.4 12 May 2017 M1 L2 — No Details →
2.0.0-beta.3 12 May 2017 M1 L2 — No Details →
2.0.0-beta.1 10 May 2017 M1 L2 — No Details →
2.0.0-alpha.9 04 May 2017 M1 L2 — No Details →
2.0.0-alpha.8 02 May 2017 M1 L2 — No Details →
2.0.0-alpha.7 01 May 2017 M1 L2 — No Details →
0.6.6 01 May 2017 M1 L2 — No Details →
2.0.0-alpha.5 25 Apr 2017 M1 L2 — No Details →
2.0.0-alpha.4 24 Apr 2017 M1 L2 — No Details →
0.6.5 10 Mar 2017 M1 L2 — No Details →
0.6.4 09 Mar 2017 M1 L2 — No Details →
0.6.3 22 Nov 2016 M1 L2 — No Details →
0.6.2 03 Jun 2016 M1 L2 — No Details →

The newest 120 of 168 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rollbar

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-62517: rollbar Prototype Pollution Vulnerability in merge() Function 5.9 medium 2.26.5 23 Oct 2025
CVE-2025-57325: rollbar Prototype Pollution Vulnerability 2.9 low No fix published 24 Sep 2025
CVE-2025-57325: rollbar Prototype Pollution Vulnerability 2.9 low 2.26.5 20 Oct 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rollbar

Is rollbar safe to use?

Vulert records 3 vulnerabilities for rollbar in npm: 0 critical, 0 high, 1 medium and 2 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is rollbar's Vulert package health score?

Vulert scores rollbar 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of rollbar affected?

Yes. 4.1.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does rollbar have?

3 vulnerabilities are recorded for rollbar in the npm ecosystem: 0 critical, 0 high, 1 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rollbar vulnerabilities disclosed?

1 vulnerability was recorded for rollbar in the last 12 months, and the oldest entry in this database dates to 24 Sep 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rollbar are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rollbar for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rollbar version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.