VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

preact: vulnerability history, versions and safety

preact is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 5 releases, from Sep 2020 to Jan 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
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 07 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all preact vulnerabilities

Vulert verdict on preact 11.0.1 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 11.0.1 — unaffected i
  • Vulnerabilities on record 2 over 5 years · 1 in the last year i
  • Latest disclosure 07 Jan 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 121 packages i
  • Stars 38,934 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i
  • Similar names @emotion/react, @testing-library/react, @types/react 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 preact, 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
11.0.1 08 Oct 2026 none MIT — Details →
11.0.0 30 Sep 2026 none MIT — Details →
11.0.0-rc.2 08 Sep 2026 none MIT — Details →
11.0.0-rc.1 26 Aug 2026 none MIT — Details →
11.0.0-rc.0 10 Aug 2026 none MIT — Details →
10.29.8 01 Aug 2026 none MIT — Details →
11.0.0-beta.2 15 Jul 2026 none MIT — Details →
10.29.7 08 Jul 2026 none MIT — Details →
10.29.6 07 Jul 2026 none MIT — Details →
10.29.5 07 Jul 2026 none MIT — Details →
10.29.4 03 Jul 2026 none MIT — Details →
10.29.3 26 Jun 2026 none MIT — Details →
10.29.2 17 May 2026 none MIT — Details →
10.29.1 03 Apr 2026 none MIT — Details →
10.29.0 10 Mar 2026 none MIT — Details →
10.28.4 19 Feb 2026 none MIT — Details →
11.0.0-beta.1 15 Feb 2026 none MIT — Details →
10.28.3 31 Jan 2026 none MIT — Details →
10.26.10 06 Jan 2026 none MIT — Details →
10.27.3 06 Jan 2026 none MIT — Details →
10.28.2 06 Jan 2026 none MIT — Details →
10.28.1 23 Dec 2025 none MIT — Details →
10.28.0 01 Dec 2025 none MIT — Details →
10.27.2 13 Sep 2025 none MIT — Details →
11.0.0-beta.0 19 Aug 2025 none MIT — Details →
10.27.1 18 Aug 2025 none MIT — Details →
10.27.0 28 Jul 2025 none MIT — Details →
10.26.9 11 Jun 2025 H1 MIT Yes Details →
10.26.8 29 May 2025 H1 MIT Yes Details →
10.26.7 24 May 2025 H1 MIT Yes Details →
10.26.6 06 May 2025 H1 MIT Yes Details →
10.26.5 06 Apr 2025 H1 MIT Yes Details →
10.26.4 28 Feb 2025 none MIT — Details →
10.26.3 27 Feb 2025 none MIT — Details →
10.26.2 18 Feb 2025 none MIT — Details →
10.26.1 18 Feb 2025 none MIT — Details →
10.26.0 16 Feb 2025 none MIT — Details →
10.25.4 28 Dec 2024 none MIT — Details →
10.25.3 18 Dec 2024 none MIT — Details →
10.25.2 12 Dec 2024 none MIT — Details →
10.25.1 02 Dec 2024 none MIT — Details →
10.25.0 22 Nov 2024 none MIT — Details →
10.24.3 14 Oct 2024 none MIT — Details →
10.24.2 04 Oct 2024 none MIT — Details →
10.24.1 24 Sep 2024 none MIT — Details →
10.24.0 14 Sep 2024 none MIT — Details →
10.23.2 12 Aug 2024 none MIT — Details →
10.23.1 25 Jul 2024 none MIT — Details →
10.23.0 23 Jul 2024 none MIT — Details →
10.22.1 01 Jul 2024 none MIT — Details →
10.22.0 15 May 2024 none MIT — Details →
10.21.0 30 Apr 2024 none MIT — Details →
10.20.2 09 Apr 2024 none MIT — Details →
10.20.1 23 Mar 2024 none MIT — Details →
10.20.0 20 Mar 2024 none MIT — Details →
10.19.7 18 Mar 2024 none MIT — Details →
10.19.6 22 Feb 2024 none MIT — Details →
10.19.5 16 Feb 2024 none MIT — Details →
10.19.4 08 Feb 2024 none MIT — Details →
10.19.3 08 Dec 2023 none MIT — Details →
10.19.2 14 Nov 2023 none MIT — Details →
10.19.1 11 Nov 2023 none MIT — Details →
10.19.0 11 Nov 2023 none MIT — Details →
10.18.2 03 Nov 2023 none MIT — Details →
10.18.1 01 Oct 2023 none MIT — Details →
10.18.0 28 Sep 2023 none MIT — Details →
10.17.1 19 Aug 2023 none MIT — Details →
10.17.0 14 Aug 2023 none MIT — Details →
10.16.0 09 Jul 2023 none MIT — Details →
10.15.1 27 May 2023 none MIT — Details →
10.15.0 21 May 2023 none MIT — Details →
10.14.1 16 May 2023 none MIT — Details →
10.14.0 14 May 2023 none MIT — Details →
10.13.2 27 Mar 2023 none MIT — Details →
10.13.1 09 Mar 2023 none MIT — Details →
10.13.0 24 Feb 2023 none MIT — Details →
10.12.1 09 Feb 2023 none MIT — Details →
10.12.0 06 Feb 2023 none MIT — Details →
10.11.3 14 Nov 2022 none MIT — Details →
10.11.2 15 Oct 2022 none MIT — Details →
10.11.1 04 Oct 2022 none MIT — Details →
10.11.0 12 Sep 2022 none MIT — Details →
10.10.6 19 Aug 2022 none MIT — Details →
10.10.5 19 Aug 2022 none MIT — Details →
10.10.4 18 Aug 2022 none MIT — Details →
10.10.3 16 Aug 2022 none MIT — Details →
10.10.2 10 Aug 2022 none MIT — Details →
10.10.1 05 Aug 2022 none MIT — Details →
10.10.0 13 Jul 2022 none MIT — Details →
10.9.0 06 Jul 2022 none MIT — Details →
10.8.2 22 Jun 2022 none MIT — Details →
10.8.1 16 Jun 2022 none MIT — Details →
10.8.0 14 Jun 2022 none MIT — Details →
10.7.3 01 Jun 2022 none MIT — Details →
10.7.2 06 May 2022 none MIT — Details →
10.7.1 05 Apr 2022 none MIT — Details →
10.7.0 29 Mar 2022 none MIT — Details →
11.0.0-experimental.1 20 Feb 2022 none MIT — Details →
11.0.0-experimental.0 20 Feb 2022 none MIT — Details →
10.6.6 14 Feb 2022 none MIT — Details →
10.6.5 27 Jan 2022 none — — Details →
10.6.4 09 Dec 2021 none — — Details →
10.6.3 08 Dec 2021 none — — Details →
10.6.2 29 Nov 2021 none — — Details →
10.6.1 25 Nov 2021 none — — Details →
10.6.0 23 Nov 2021 none — — Details →
10.5.15 12 Oct 2021 none — — Details →
10.5.14 01 Jul 2021 none — — Details →
10.5.13 14 Mar 2021 none — — Details →
10.5.12 26 Jan 2021 none — — Details →
10.5.11 20 Jan 2021 none — — Details →
10.5.10 14 Jan 2021 none — — Details →
10.5.9 03 Jan 2021 none — — Details →
10.5.8 30 Dec 2020 none — — Details →
10.5.7 12 Nov 2020 none — — Details →
10.5.6 12 Nov 2020 none — — Details →
10.5.5 18 Oct 2020 none — — Details →
10.5.4 05 Oct 2020 none — — Details →
10.5.3 28 Sep 2020 none — — Details →
10.5.2 23 Sep 2020 none — — 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

  • 2020 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for preact

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-22028: Preact JSON VNode Injection Vulnerability 7.2 high 10.26.10 07 Jan 2026
HTML Injection in preact N/A medium 10.0.0-beta.1 02 Sep 2020

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 preact

Is preact safe to use?

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

Vulert scores preact 84/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 preact affected?

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

Which version of preact should I use?

11.0.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 preact have?

2 vulnerabilities are recorded for preact in the npm ecosystem: 0 critical, 1 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 preact vulnerabilities disclosed?

1 vulnerability was recorded for preact in the last 12 months, and the oldest entry in this database dates to 02 Sep 2020. 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 preact 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 preact for upcoming vulnerabilities?

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