VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

link-preview-js: vulnerability history, versions and safety

link-preview-js is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 47 releases, from Jul 2022 to 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
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all link-preview-js vulnerabilities

Vulert verdict on link-preview-js 5.0.1 i

Updated on 22 Oct 2026

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

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

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

  • Current release 5.0.1 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 2 in the last year i
  • Latest disclosure 02 Sep 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 910 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 link-preview-js, 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.0.1 14 Oct 2026 none MIT — Details →
5.0.0 31 Jul 2026 none MIT — Details →
5.0.0-beta.0 03 Jul 2026 none MIT — Details →
4.0.4 23 Jun 2026 none MIT — Details →
4.0.3 12 May 2026 H1 MIT Yes Details →
4.0.1 25 Apr 2026 H1 MIT Yes Details →
4.0.0 20 Nov 2025 H2 MIT Yes Details →
3.2.0 14 Nov 2025 H2 MIT Yes Details →
3.1.0 26 May 2025 H2 MIT Yes Details →
3.0.15 17 May 2025 H2 MIT Yes Details →
3.0.14 10 Feb 2025 H2 MIT Yes Details →
3.0.13 04 Jan 2025 H2 MIT Yes Details →
3.0.12 21 Oct 2024 H2 MIT Yes Details →
3.0.11 21 Oct 2024 H2 MIT Yes Details →
3.0.10 21 Oct 2024 H2 MIT Yes Details →
3.0.9 21 Oct 2024 H2 MIT Yes Details →
3.0.6 21 Oct 2024 H2 MIT Yes Details →
3.0.5 16 Aug 2023 H2 MIT Yes Details →
3.0.4 08 Sep 2022 H2 MIT Yes Details →
3.0.3 29 Jul 2022 H2 MIT Yes Details →
3.0.2 27 Jul 2022 H2 MIT Yes Details →
3.0.0 09 Jul 2022 H2 MIT Yes Details →
2.1.19 06 Jul 2022 H2 MIT Yes Details →
2.1.17 04 Jul 2022 H2 MIT Yes Details →
2.1.16 27 Jun 2022 H2 M1 MIT Yes Details →
2.1.15 26 May 2022 H2 M1 MIT Yes Details →
2.1.14 26 May 2022 H2 M1 MIT Yes Details →
2.1.13 08 Feb 2022 H2 M1 MIT Yes Details →
2.1.12 07 Feb 2022 H2 M1 MIT Yes Details →
2.1.11 07 Feb 2022 H2 M1 MIT Yes Details →
2.1.10 17 Jan 2022 H2 M1 MIT Yes Details →
2.1.9 17 Jan 2022 H2 M1 MIT Yes Details →
2.1.8 25 Jul 2021 H2 M1 MIT Yes Details →
2.1.7 23 Jul 2021 H2 M1 MIT Yes Details →
2.1.6 20 Feb 2021 H2 M1 MIT Yes Details →
2.1.5 20 Feb 2021 H2 M1 MIT Yes Details →
2.1.4 20 Feb 2021 H2 M1 MIT Yes Details →
2.1.3 25 Dec 2020 H2 M1 MIT Yes Details →
2.1.2 23 Dec 2020 H2 M1 MIT Yes Details →
2.1.1 11 Dec 2020 H2 M1 MIT Yes Details →
2.1.0 04 Dec 2020 H2 M1 MIT Yes Details →
2.0.5 30 Oct 2020 H2 M1 MIT Yes Details →
2.0.4 08 May 2020 H2 M1 MIT Yes Details →
2.0.3 08 May 2020 H2 M1 MIT Yes Details →
2.0.2 30 Apr 2020 H2 M1 MIT Yes Details →
2.0.1 07 Jan 2020 H2 M1 MIT Yes Details →
2.0.0 07 Jan 2020 H2 M1 MIT Yes Details →
1.6.0 03 Jan 2020 H2 M1 MIT Yes Details →
1.5.0 31 Oct 2019 H2 M1 MIT Yes Details →
1.4.4 29 Oct 2019 H2 M1 MIT Yes Details →
1.4.3 06 Oct 2019 H2 M1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for link-preview-js

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-43897: link-preview-js Vulnerable to IPv6 and Internal Loopback Attacks 8.7 high 4.0.1 05 May 2026
CVE-2026-61704: link-preview-js DNS Rebinding SSRF Bypass - Incomplete Fix 7.5 high 4.0.4 02 Sep 2026
CVE-2022-25876: Server-Side Request Forgery in link-preview-js 5.5 medium 2.1.17 02 Jul 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 link-preview-js

Is link-preview-js safe to use?

Vulert records 3 vulnerabilities for link-preview-js in npm: 0 critical, 2 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 link-preview-js's Vulert package health score?

Vulert scores link-preview-js 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 link-preview-js affected?

No. 5.0.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.

How many vulnerabilities does link-preview-js have?

3 vulnerabilities are recorded for link-preview-js in the npm ecosystem: 0 critical, 2 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 link-preview-js vulnerabilities disclosed?

2 vulnerabilities were recorded for link-preview-js in the last 12 months, and the oldest entry in this database dates to 02 Jul 2022. 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 link-preview-js 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 link-preview-js for upcoming vulnerabilities?

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