Vulnerability Database · npm · Package report

@rails/actioncable: vulnerability history, versions and safety

@rails/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.

Vulert verdict on @rails/actioncable 8.1.400 i

Updated on 23 Oct 2026

Good news: 8.1.400, the version you would install today, has no known vulnerabilities.

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 8.1.400 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 58 packages i
  • Stars 58,850 i
  • OpenSSF scorecard 5/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 @rails/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
7.2.400 24 Sep 2026 none MIT — Details →
8.1.400 24 Sep 2026 none MIT — Details →
8.0.501 29 Jul 2026 none MIT — Details →
7.2.302 29 Jul 2026 none MIT — Details →
8.1.301 29 Jul 2026 none MIT — Details →
8.1.300 24 Mar 2026 none MIT — Details →
8.0.500 24 Mar 2026 none MIT — Details →
8.1.201 23 Mar 2026 none MIT — Details →
8.0.401 23 Mar 2026 none MIT — Details →
7.2.301 23 Mar 2026 none MIT — Details →
8.1.200 08 Jan 2026 none MIT — Details →
8.1.100 28 Oct 2025 none MIT — Details →
8.0.400 28 Oct 2025 none MIT — Details →
7.2.300 28 Oct 2025 none MIT — Details →
7.1.600 28 Oct 2025 none MIT — Details →
7.0.1000 28 Oct 2025 none MIT — Details →
8.1.0 22 Oct 2025 none MIT — Details →
8.1.0-rc1 15 Oct 2025 none MIT — Details →
8.0.300 22 Sep 2025 none MIT — Details →
8.1.0-beta1 04 Sep 2025 none MIT — Details →
8.0.201 13 Aug 2025 none MIT — Details →
7.2.202 13 Aug 2025 none MIT — Details →
7.1.502 13 Aug 2025 none MIT — Details →
8.0.200 12 Mar 2025 none MIT — Details →
8.0.100 13 Dec 2024 none MIT — Details →
8.0.1 10 Dec 2024 none MIT — Details →
7.2.201 10 Dec 2024 none MIT — Details →
7.1.501 10 Dec 2024 none MIT — Details →
7.0.807 10 Dec 2024 none MIT — Details →
8.0.0 07 Nov 2024 none MIT — Details →
7.2.200 31 Oct 2024 none MIT — Details →
7.1.500 31 Oct 2024 none MIT — Details →
8.0.0-rc2 30 Oct 2024 none MIT — Details →
7.2.102 23 Oct 2024 none MIT — Details →
7.1.402 23 Oct 2024 none MIT — Details →
7.0.806 23 Oct 2024 none MIT — Details →
6.1.710 23 Oct 2024 none MIT — Details →
8.0.0-rc1 19 Oct 2024 none MIT — Details →
6.1.709 15 Oct 2024 none MIT — Details →
7.2.101 15 Oct 2024 none MIT — Details →
7.1.401 15 Oct 2024 none MIT — Details →
7.0.805 15 Oct 2024 none MIT — Details →
8.0.0-beta1 26 Sep 2024 none MIT — Details →
7.1.400 22 Aug 2024 none MIT — Details →
7.2.100 22 Aug 2024 none MIT — Details →
7.2.0 09 Aug 2024 none MIT — Details →
7.2.0-rc1 06 Aug 2024 none MIT — Details →
7.2.0-beta3 11 Jul 2024 none MIT — Details →
7.2.0-beta2 04 Jun 2024 none MIT — Details →
7.1.3-4 04 Jun 2024 none MIT — Details →
7.0.8-4 04 Jun 2024 none MIT — Details →
6.1.7-8 04 Jun 2024 none MIT — Details →
7.2.0-beta1 29 May 2024 none MIT — Details →
7.0.8-3 17 May 2024 none MIT — Details →
7.1.3-3 16 May 2024 none MIT — Details →
7.0.8-2 16 May 2024 none MIT — Details →
7.1.3-2 21 Feb 2024 none MIT — Details →
7.1.3-1 21 Feb 2024 none MIT — Details →
7.0.8-1 21 Feb 2024 none MIT — Details →
6.1.7-7 21 Feb 2024 none MIT — Details →
7.1.3 16 Jan 2024 none MIT — Details →
7.1.2 10 Nov 2023 none MIT — Details →
7.1.1 11 Oct 2023 none MIT — Details →
7.1.0 05 Oct 2023 none MIT — Details →
7.1.0-rc2 01 Oct 2023 none MIT — Details →
7.1.0-rc1 27 Sep 2023 none MIT — Details →
7.1.0-beta1 13 Sep 2023 none MIT — Details →
7.0.8 09 Sep 2023 none MIT — Details →
7.0.7-2 22 Aug 2023 none MIT — Details →
6.1.7-6 22 Aug 2023 none MIT — Details →
7.0.7-1 22 Aug 2023 none MIT — Details →
6.1.7-5 22 Aug 2023 none MIT — Details →
7.0.7 09 Aug 2023 none MIT — Details →
7.0.6 29 Jun 2023 none MIT — Details →
7.0.5-1 26 Jun 2023 none MIT — Details →
6.1.7-4 26 Jun 2023 none MIT — Details →
7.0.5 24 May 2023 none MIT — Details →
7.0.4-3 13 Mar 2023 none MIT — Details →
6.1.7-3 13 Mar 2023 none MIT — Details →
6.1.7-2 25 Jan 2023 none MIT — Details →
7.0.4-2 25 Jan 2023 none MIT — Details →
7.0.4-1 17 Jan 2023 none MIT — Details →
6.1.7-1 17 Jan 2023 none MIT — Details →
6.0.6-1 17 Jan 2023 none MIT — Details →
7.0.4 09 Sep 2022 none MIT — Details →
6.1.7 09 Sep 2022 none MIT — Details →
6.0.6 09 Sep 2022 none MIT — Details →
7.0.3-1 12 Jul 2022 none MIT — Details →
6.1.6-1 12 Jul 2022 none MIT — Details →
6.0.5-1 12 Jul 2022 none MIT — Details →
6.0.5 09 May 2022 none MIT — Details →
6.1.6 09 May 2022 none MIT — Details →
7.0.3 09 May 2022 none MIT — Details →
7.0.2-4 26 Apr 2022 none MIT — Details →
6.1.5-1 26 Apr 2022 none MIT — Details →
6.0.4-8 26 Apr 2022 none MIT — Details →
6.1.5 10 Mar 2022 none MIT — Details →
7.0.2-3 08 Mar 2022 none MIT — Details →
6.1.4-7 08 Mar 2022 none MIT — Details →
6.0.4-7 08 Mar 2022 none MIT — Details →
7.0.2-2 11 Feb 2022 none — — Details →
6.1.4-6 11 Feb 2022 none — — Details →
6.0.4-6 11 Feb 2022 none — — Details →
6.0.4-5 11 Feb 2022 none — — Details →
6.1.4-5 11 Feb 2022 none — — Details →
7.0.2-1 11 Feb 2022 none — — Details →
7.0.2 08 Feb 2022 none — — Details →
7.0.1 06 Jan 2022 none — — Details →
7.0.0 15 Dec 2021 none — — Details →
6.1.4-4 15 Dec 2021 none — — Details →
6.0.4-4 15 Dec 2021 none — — Details →
7.0.0-rc3 14 Dec 2021 none — — Details →
6.1.4-3 14 Dec 2021 none — — Details →
6.0.4-3 14 Dec 2021 none — — Details →
6.0.4-2 14 Dec 2021 none — — Details →
6.1.4-2 14 Dec 2021 none — — Details →
7.0.0-rc2 14 Dec 2021 none — — Details →
7.0.0-rc1 06 Dec 2021 none — — Details →
7.0.0-alpha2 15 Sep 2021 none — — Details →
7.0.0-alpha1 15 Sep 2021 none — — Details →

The newest 120 of 156 versions Vulert tracks. 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 @rails/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 @rails/actioncable

Is @rails/actioncable safe to use?

Vulert has no vulnerabilities on record for @rails/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 @rails/actioncable's Vulert package health score?

Vulert scores @rails/actioncable 86/100, which reads as healthy. 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 @rails/actioncable affected?

No. 8.1.400, 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 @rails/actioncable should I use?

8.1.400 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 @rails/actioncable have?

0 vulnerabilities are recorded for @rails/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 @rails/actioncable vulnerabilities disclosed?

0 vulnerabilities were recorded for @rails/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 @rails/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 @rails/actioncable for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @rails/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.