VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@libp2p/peer-store: vulnerability history, versions and safety

@libp2p/peer-store is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 58 releases, first recorded in Sep 2026. 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 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 17 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @libp2p/peer-store vulnerabilities

Vulert verdict on @libp2p/peer-store 12.0.32 i

Updated on 23 Oct 2026

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

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

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

  • Current release 12.0.32 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 17 Sep 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 358 packages i
  • Stars 2,584 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 OR 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 @libp2p/peer-store, 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
12.0.32 19 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31-7fa88999d 19 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31-c57bf6228 19 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31-3da8bab7c 19 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31-b927d5921 18 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31-aa5ba42d0 18 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.31 18 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-2d4c93ed6 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-d1ce8bdbe 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-95392efdf 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-f0e64b9b8 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-57c4b4456 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30-6d888970e 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.30 17 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-be63a4416 16 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-e48eabf67 16 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-e073d373d 15 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-4a416447c 12 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-974e63f20 11 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29-5c4cdb2d6 10 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.29 10 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-e724dd173 10 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-9441e049a 10 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-fc90066f8 08 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-40480a034 05 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-235711723 05 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-16fba5630 03 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-183116ba0 03 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-a9bae64cb 03 Oct 2026 none Apache-2.0 OR MIT — Details →
12.0.28-776cdedf6 27 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-e7359e5f6 27 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-2f63792c7 27 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-fb139d1c8 23 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-d91797b55 16 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-5cb617ae2 02 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28-185d901cd 02 Sep 2026 none Apache-2.0 OR MIT — Details →
12.0.28 31 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.27-cef4d32cf 31 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.27-ac7305ccf 31 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.27-87dca02b0 27 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.27-4a6c5d11a 27 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.27 23 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-947d304ed 22 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-0967e75f5 22 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-4dae661b4 22 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-8786aa8d0 20 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-55d7a539a 20 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-d5534174d 13 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26-47cf9cdc1 10 Aug 2026 none Apache-2.0 OR MIT — Details →
12.0.26 30 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.25-ef6e1851c 30 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.25-423335b45 30 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.25 26 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-5927b62d6 26 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-68794c8e2 26 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-b500071e4 26 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.24-d9292b690 24 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.24-7f5500989 24 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-868b33379 20 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-e86b39e5d 20 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.24-05b15b2b1 19 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-02fcf704d 19 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-382fbb4ca 19 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24-dee9df67f 19 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.24-d96b30ebd 19 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.24-99b23b2a0 19 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.24 19 Jul 2026 none Apache-2.0 OR MIT — Details →
12.0.23-ff9e5fc7c 19 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-523b52bd6 19 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-5459e136d 18 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-bd7f0cda6 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-3bf5d395c 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-89335e39f 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-ba1551199 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-cec2b1f34 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-084ad7890 17 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-fb9e8a76e 16 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-a04f5e0bf 15 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23-4bb8fbe8d 08 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.23 07 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-dd084c0b2 07 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-08898d7df 07 Jul 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-f144def15 22 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-47a51e3d1 20 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-d4dad9bf5 20 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22-bfb7ceb0f 20 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.22 13 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.21-5e07d5963 13 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.21-404c7824a 12 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.21-7ae12f9b0 06 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.21-a34745c01 05 Jun 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.21 31 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-160a24585 30 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-5b8813abc 30 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-b7c6dc0f2 29 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-29797a5bb 29 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-d888f182f 27 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-ed1ad1f26 25 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-3574648c3 25 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-d59c165ac 18 May 2026 H1 Apache-2.0 OR MIT Yes Details →
12.0.20-b9ebef660 17 May 2026 H1 — Yes Details →
12.0.20 16 May 2026 H1 — Yes Details →
12.0.19-cc151e147 16 May 2026 H1 — Yes Details →
12.0.19-9eb27be79 15 May 2026 H1 — Yes Details →
12.0.19-5692f3f16 13 May 2026 H1 — Yes Details →
12.0.19-9c3c0b22a 12 May 2026 H1 — Yes Details →
12.0.19 11 May 2026 H1 — Yes Details →
12.0.18-15eeedba1 09 May 2026 H1 — Yes Details →
12.0.18-bd9e02dad 09 May 2026 H1 — Yes Details →
12.0.18-d1ab98294 04 May 2026 H1 — Yes Details →
12.0.18-3a5e46eaa 29 Apr 2026 H1 — Yes Details →
12.0.18-10b2bdf50 26 Apr 2026 H1 — Yes Details →
12.0.18 25 Apr 2026 H1 — Yes Details →
12.0.17-baf3ddb03 25 Apr 2026 H1 — Yes Details →
12.0.17-61d594a6c 25 Apr 2026 H1 — Yes Details →
12.0.17-d57fe74c0 24 Apr 2026 H1 — Yes Details →
12.0.17-5466a8def 24 Apr 2026 H1 — Yes Details →
12.0.17-cbfda2cdc 23 Apr 2026 H1 — Yes Details →
12.0.17-69a44651f 22 Apr 2026 H1 — Yes Details →
12.0.17-fd68eecf7 20 Apr 2026 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @libp2p/peer-store

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-86039: @libp2p/peer-store PeerRecord Vulnerability Leading to Address Poisoning 8.2 high 12.0.24 17 Sep 2026

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 @libp2p/peer-store

Is @libp2p/peer-store safe to use?

Vulert records 1 vulnerabilities for @libp2p/peer-store in npm: 0 critical, 1 high, 0 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 @libp2p/peer-store's Vulert package health score?

Vulert scores @libp2p/peer-store 81/100, which reads as in good shape. 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 @libp2p/peer-store affected?

No. 12.0.32, 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 @libp2p/peer-store have?

1 vulnerability is recorded for @libp2p/peer-store in the npm ecosystem: 0 critical, 1 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 @libp2p/peer-store vulnerabilities disclosed?

1 vulnerability was recorded for @libp2p/peer-store in the last 12 months, and the oldest entry in this database dates to 17 Sep 2026. 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 @libp2p/peer-store 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 @libp2p/peer-store for upcoming vulnerabilities?

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