VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pubnub: vulnerability history, versions and safety

pubnub is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 33 releases, first recorded in Dec 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 pubnub vulnerabilities

Vulert verdict on pubnub 13.1.3 i

Updated on 23 Oct 2026

Good news: 13.1.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 13.1.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 06 Dec 2023 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Stars 561 i
  • Last release this month i
  • Licence non-standard 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 pubnub, 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
13.1.3 22 Oct 2026 none non-standard — Details →
13.1.2 14 Oct 2026 none non-standard — Details →
13.1.1 13 Oct 2026 none non-standard — Details →
13.1.0 12 Oct 2026 none non-standard — Details →
13.0.3 22 Sep 2026 none non-standard — Details →
13.0.2 21 Sep 2026 none non-standard — Details →
13.0.1 10 Sep 2026 none non-standard — Details →
13.0.0 08 Sep 2026 none non-standard — Details →
12.0.3 27 Jul 2026 none non-standard — Details →
12.0.2 22 Jul 2026 none non-standard — Details →
12.0.1 21 Jul 2026 none non-standard — Details →
12.0.0 22 Jun 2026 none non-standard — Details →
11.0.2 11 Jun 2026 none non-standard — Details →
11.0.1 13 May 2026 none non-standard — Details →
11.0.0 20 Apr 2026 none non-standard — Details →
10.2.9 16 Mar 2026 none non-standard — Details →
10.2.8 10 Mar 2026 none non-standard — Details →
10.2.7 12 Feb 2026 none non-standard — Details →
10.2.6 13 Jan 2026 none non-standard — Details →
10.2.5 16 Dec 2025 none non-standard — Details →
10.2.4 04 Dec 2025 none non-standard — Details →
10.2.3 20 Nov 2025 none non-standard — Details →
10.2.2 19 Nov 2025 none non-standard — Details →
10.2.1 10 Nov 2025 none non-standard — Details →
10.2.0 02 Nov 2025 none non-standard — Details →
10.1.0 30 Sep 2025 none non-standard — Details →
10.0.0 18 Sep 2025 none non-standard — Details →
9.11.0 18 Sep 2025 none non-standard — Details →
9.10.0 09 Sep 2025 none non-standard — Details →
9.9.0 25 Aug 2025 none non-standard — Details →
9.8.4 07 Aug 2025 none non-standard — Details →
9.8.3 28 Jul 2025 none non-standard — Details →
9.8.1 15 Jul 2025 none non-standard — Details →
9.8.0 11 Jul 2025 none non-standard — Details →
9.7.0 30 Jun 2025 none non-standard — Details →
9.6.2 30 Jun 2025 none non-standard — Details →
9.6.1 18 Jun 2025 none non-standard — Details →
9.6.0 04 Jun 2025 none non-standard — Details →
9.5.2 22 Apr 2025 none non-standard — Details →
9.5.1 15 Apr 2025 none non-standard — Details →
9.5.0 15 Apr 2025 none non-standard — Details →
9.4.0 10 Apr 2025 none non-standard — Details →
9.3.2 31 Mar 2025 none non-standard — Details →
9.3.1 25 Mar 2025 none non-standard — Details →
9.3.0 20 Mar 2025 none non-standard — Details →
9.2.0 19 Mar 2025 none non-standard — Details →
9.1.0 13 Mar 2025 none non-standard — Details →
9.0.0 10 Mar 2025 none non-standard — Details →
8.10.0 06 Mar 2025 none non-standard — Details →
8.9.1 26 Feb 2025 none non-standard — Details →
8.9.0 18 Feb 2025 none non-standard — Details →
8.8.1 10 Feb 2025 none non-standard — Details →
8.8.0 05 Feb 2025 none non-standard — Details →
8.7.1 31 Jan 2025 none non-standard — Details →
8.7.0 30 Jan 2025 none non-standard — Details →
8.6.0 21 Jan 2025 none non-standard — Details →
8.5.0 15 Jan 2025 none non-standard — Details →
8.4.1 02 Jan 2025 none non-standard — Details →
8.4.0 17 Dec 2024 none non-standard — Details →
8.3.2 12 Dec 2024 none non-standard — Details →
8.3.1 18 Nov 2024 none non-standard — Details →
8.3.0 14 Nov 2024 none non-standard — Details →
8.2.10 31 Oct 2024 none non-standard — Details →
8.2.9 25 Oct 2024 none non-standard — Details →
8.2.8 30 Sep 2024 none non-standard — Details →
8.2.7 01 Aug 2024 none non-standard — Details →
8.2.6 23 Jul 2024 none non-standard — Details →
8.2.5 04 Jul 2024 none non-standard — Details →
8.2.4 17 Jun 2024 none non-standard — Details →
8.2.3 06 Jun 2024 none non-standard — Details →
8.2.2 05 Jun 2024 none non-standard — Details →
8.2.1 22 May 2024 none non-standard — Details →
8.2.0 21 May 2024 none non-standard — Details →
8.1.0 16 May 2024 none non-standard — Details →
8.0.1 23 Apr 2024 none non-standard — Details →
8.0.0 22 Apr 2024 none non-standard — Details →
7.6.3 18 Apr 2024 none non-standard — Details →
7.6.2 28 Mar 2024 none non-standard — Details →
7.6.1 26 Feb 2024 none non-standard — Details →
7.6.0 21 Feb 2024 none non-standard — Details →
7.5.0 16 Jan 2024 none non-standard — Details →
7.4.5 28 Nov 2023 none non-standard — Details →
7.4.4 14 Nov 2023 none non-standard — Details →
7.4.3 08 Nov 2023 none non-standard — Details →
7.4.2 30 Oct 2023 none non-standard — Details →
7.4.1 17 Oct 2023 none MIT — Details →
7.4.0 16 Oct 2023 none MIT — Details →
7.3.3 11 Sep 2023 M1 MIT Yes Details →
7.3.2 31 Aug 2023 M1 MIT Yes Details →
7.3.1 21 Aug 2023 M1 MIT Yes Details →
7.3.0 28 Jul 2023 M1 MIT Yes Details →
7.2.3 23 Jun 2023 M1 MIT Yes Details →
7.2.2 13 Dec 2022 M1 MIT Yes Details →
7.2.1 14 Nov 2022 M1 MIT Yes Details →
7.2.0 05 Jul 2022 M1 MIT Yes Details →
7.1.2 22 Jun 2022 M1 MIT Yes Details →
7.1.1 14 Jun 2022 M1 MIT Yes Details →
7.0.1 24 May 2022 M1 MIT Yes Details →
7.0.0 24 May 2022 M1 MIT Yes Details →
5.0.1 02 Mar 2022 M1 MIT Yes Details →
5.0.0 12 Jan 2022 M1 — Yes Details →
4.37.0 16 Dec 2021 M1 — Yes Details →
4.36.0 09 Dec 2021 M1 — Yes Details →
4.35.0 06 Dec 2021 M1 — Yes Details →
4.34.2 01 Dec 2021 M1 — Yes Details →
4.34.1 22 Nov 2021 M1 — Yes Details →
4.34.0 19 Nov 2021 M1 — Yes Details →
4.33.1 18 Oct 2021 M1 — Yes Details →
4.33.0 31 Aug 2021 M1 — Yes Details →
4.32.1 26 May 2021 M1 — Yes Details →
4.32.0 28 Apr 2021 M1 — Yes Details →
4.31.0 22 Apr 2021 M1 — Yes Details →
4.30.1 30 Mar 2021 M1 — Yes Details →
4.30.0 30 Mar 2021 M1 — Yes Details →
4.29.11 11 Jan 2021 M1 — Yes Details →
4.29.10 30 Nov 2020 M1 — Yes Details →
4.29.9 05 Oct 2020 M1 — Yes Details →
4.29.8 22 Sep 2020 M1 — Yes Details →
4.29.8-rc1 19 Sep 2020 M1 — Yes Details →
4.29.7 14 Sep 2020 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for pubnub

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-26154: pubnub Insufficient Entropy vulnerability 5.9 medium 7.4.0 06 Dec 2023

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 pubnub

Is pubnub safe to use?

Vulert records 1 vulnerabilities for pubnub in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pubnub's Vulert package health score?

Vulert scores pubnub 90/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 pubnub affected?

No. 13.1.3, 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.

How many vulnerabilities does pubnub have?

1 vulnerability is recorded for pubnub in the npm ecosystem: 0 critical, 0 high, 1 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 pubnub vulnerabilities disclosed?

0 vulnerabilities were recorded for pubnub in the last 12 months, and the oldest entry in this database dates to 06 Dec 2023. 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 pubnub 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 pubnub for upcoming vulnerabilities?

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