VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

actioncable: vulnerability history, versions and safety

actioncable is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all actioncable vulnerabilities

Vulert verdict on actioncable 5.2.8-1 i

Updated on 23 Oct 2026

Good news: 5.2.8-1, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Moderate

What to do: Stay on 5.2.8-1 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.2.8-1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.2.8-1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 58,850 i
  • OpenSSF scorecard 5/10 i
  • Last release 51 months ago 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 actioncable, 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
5.2.8-1 12 Jul 2022 none MIT — Details →
5.2.8 09 May 2022 none MIT — Details →
5.2.7-1 26 Apr 2022 none MIT — Details →
5.2.7 11 Mar 2022 none MIT — Details →
5.2.6-3 08 Mar 2022 none MIT — Details →
5.2.6-2 11 Feb 2022 none MIT — Details →
5.2.6-1 11 Feb 2022 none MIT — Details →
5.2.6 05 May 2021 none MIT — Details →
5.2.4-6 05 May 2021 none MIT — Details →
5.2.5 26 Mar 2021 none MIT — Details →
5.2.4-5 10 Feb 2021 none MIT — Details →
5.2.4-4 09 Sep 2020 none MIT — Details →
5.2.4-3 18 May 2020 none MIT — Details →
5.2.4-2 19 Mar 2020 none MIT — Details →
5.2.4-1 18 Dec 2019 none MIT — Details →
5.2.4 27 Nov 2019 none MIT — Details →
5.2.4-rc1 23 Nov 2019 none MIT — Details →
5.2.3 28 Mar 2019 none MIT — Details →
5.1.7 28 Mar 2019 none MIT — Details →
5.1.7-rc1 22 Mar 2019 none MIT — Details →
5.2.3-rc1 22 Mar 2019 none MIT — Details →
5.2.2-1 13 Mar 2019 none MIT — Details →
5.1.6-2 13 Mar 2019 none MIT — Details →
5.0.7-2 13 Mar 2019 none MIT — Details →
5.2.2 04 Dec 2018 none MIT — Details →
5.2.2-rc1 28 Nov 2018 none MIT — Details →
5.2.1-1 27 Nov 2018 none MIT — Details →
5.1.6-1 27 Nov 2018 none MIT — Details →
5.0.7-1 27 Nov 2018 none MIT — Details →
5.2.1 07 Aug 2018 none MIT — Details →
5.2.1-rc1 30 Jul 2018 none MIT — Details →
5.2.0 09 Apr 2018 none MIT — Details →
5.1.6 29 Mar 2018 none MIT — Details →
5.0.7 29 Mar 2018 none MIT — Details →
5.2.0-rc2 20 Mar 2018 none MIT — Details →
5.1.5 14 Feb 2018 none MIT — Details →
5.1.5-rc1 01 Feb 2018 none MIT — Details →
5.2.0-rc1 30 Jan 2018 none MIT — Details →
5.2.0-beta2 28 Nov 2017 none MIT — Details →
5.2.0-beta1 27 Nov 2017 none MIT — Details →
5.1.4 08 Sep 2017 none MIT — Details →
5.0.6 08 Sep 2017 none MIT — Details →
5.1.4-rc1 24 Aug 2017 none MIT — Details →
5.0.6-rc1 24 Aug 2017 none MIT — Details →
5.1.3 03 Aug 2017 none MIT — Details →
5.1.3-rc3 31 Jul 2017 none MIT — Details →
5.0.5 31 Jul 2017 none MIT — Details →
5.0.5-rc2 25 Jul 2017 none MIT — Details →
5.1.3-rc2 25 Jul 2017 none MIT — Details →
5.0.5-rc1 19 Jul 2017 none MIT — Details →
5.1.3-rc1 19 Jul 2017 none MIT — Details →
5.1.2 26 Jun 2017 none MIT — Details →
5.1.2-rc1 20 Jun 2017 none MIT — Details →
5.0.4 19 Jun 2017 none MIT — Details →
5.0.4-rc1 14 Jun 2017 none MIT — Details →
5.1.1 12 May 2017 none MIT — Details →
5.0.3 12 May 2017 none MIT — Details →
5.1.0 27 Apr 2017 none MIT — Details →
5.1.0-rc2 21 Apr 2017 none MIT — Details →
5.1.0-rc1 20 Mar 2017 none MIT — Details →
5.0.2 01 Mar 2017 none MIT — Details →
5.0.2-rc1 25 Feb 2017 none MIT — Details →
5.1.0-beta1 23 Feb 2017 none MIT — Details →
5.0.1 21 Dec 2016 none MIT — Details →
5.0.1-rc2 09 Dec 2016 none MIT — Details →
5.0.1-rc1 30 Nov 2016 none MIT — Details →
5.0.0 30 Jun 2016 none MIT — Details →
5.0.0-beta3 06 Mar 2016 none MIT — Details →
5.0.0-beta1-3 21 Dec 2015 none MIT — Details →
5.0.0-beta1-2 21 Dec 2015 none MIT — Details →
0.1.1 21 Dec 2015 none MIT — Details →
0.1.0 21 Dec 2015 none MIT — Details →

All 72 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for actioncable

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 actioncable

Is actioncable safe to use?

Vulert has no vulnerabilities on record for actioncable in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is actioncable's Vulert package health score?

Vulert scores actioncable 61/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).

Is the latest version of actioncable affected?

No. 5.2.8-1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of actioncable should I use?

5.2.8-1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does actioncable have?

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

How often are new actioncable vulnerabilities disclosed?

0 vulnerabilities were recorded for actioncable in the last 12 months. 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 actioncable 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 actioncable for upcoming vulnerabilities?

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