VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@vitest/browser: vulnerability history, versions and safety

@vitest/browser is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 47 releases, from Feb 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @vitest/browser vulnerabilities

Vulert verdict on @vitest/browser 5.0.5 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 5.0.5 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 35 packages i
  • Stars 17,270 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 @vitest/browser, 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.1.0-beta.1 19 Oct 2026 none MIT — Details →
4.1.12 15 Oct 2026 none MIT — Details →
5.0.5 15 Oct 2026 none MIT — Details →
5.0.4 12 Oct 2026 none MIT — Details →
5.0.3 30 Sep 2026 none MIT — Details →
5.0.2 25 Sep 2026 none MIT — Details →
5.0.1 15 Sep 2026 none MIT — Details →
5.0.0 03 Sep 2026 none MIT — Details →
5.0.0-rc.4 31 Aug 2026 none MIT — Details →
5.0.0-rc.3 28 Aug 2026 none MIT — Details →
4.1.11 18 Aug 2026 none MIT — Details →
5.0.0-rc.2 17 Aug 2026 none MIT — Details →
5.0.0-rc.1 11 Aug 2026 none MIT — Details →
5.0.0-beta.7 24 Jul 2026 none MIT — Details →
5.0.0-beta.6 06 Jul 2026 none MIT — Details →
4.1.10 06 Jul 2026 none MIT — Details →
3.2.7 06 Jul 2026 none MIT — Details →
5.0.0-beta.5 15 Jun 2026 none MIT — Details →
4.1.9 15 Jun 2026 C1 MIT Yes Details →
3.2.6 01 Jun 2026 none MIT — Details →
5.0.0-beta.4 01 Jun 2026 none MIT — Details →
3.2.5 01 Jun 2026 none MIT — Details →
4.1.8 01 Jun 2026 C1 MIT Yes Details →
4.1.7 20 May 2026 C1 MIT Yes Details →
5.0.0-beta.3 19 May 2026 C1 MIT Yes Details →
4.1.6 11 May 2026 C1 MIT Yes Details →
5.0.0-beta.2 05 May 2026 C1 MIT Yes Details →
5.0.0-beta.1 23 Apr 2026 C1 MIT Yes Details →
4.1.5 21 Apr 2026 C2 MIT Yes Details →
4.1.4 09 Apr 2026 C2 MIT Yes Details →
4.1.3 07 Apr 2026 C2 MIT Yes Details →
4.1.2 26 Mar 2026 C2 MIT Yes Details →
4.1.1 23 Mar 2026 C2 MIT Yes Details →
4.1.0 12 Mar 2026 C2 MIT Yes Details →
4.1.0-beta.6 05 Mar 2026 C2 MIT Yes Details →
4.1.0-beta.5 26 Feb 2026 C2 MIT Yes Details →
4.1.0-beta.4 16 Feb 2026 C2 MIT Yes Details →
4.1.0-beta.3 02 Feb 2026 C2 MIT Yes Details →
4.0.18 22 Jan 2026 C2 MIT Yes Details →
4.1.0-beta.2 22 Jan 2026 C2 MIT Yes Details →
4.1.0-beta.1 14 Jan 2026 C2 MIT Yes Details →
4.0.17 12 Jan 2026 C2 MIT Yes Details →
4.0.16 16 Dec 2025 C1 MIT Yes Details →
4.0.15 02 Dec 2025 C1 MIT Yes Details →
4.0.14 25 Nov 2025 C1 MIT Yes Details →
4.0.13 21 Nov 2025 C1 MIT Yes Details →
4.0.12 20 Nov 2025 C1 MIT Yes Details →
4.0.11 20 Nov 2025 C1 MIT Yes Details →
4.0.10 17 Nov 2025 C1 MIT Yes Details →
4.0.9 14 Nov 2025 C1 MIT Yes Details →
4.0.8 07 Nov 2025 C1 MIT Yes Details →
4.0.7 04 Nov 2025 C1 MIT Yes Details →
4.0.6 31 Oct 2025 C1 MIT Yes Details →
4.0.5 29 Oct 2025 C1 MIT Yes Details →
4.0.4 27 Oct 2025 C1 MIT Yes Details →
4.0.3 24 Oct 2025 C1 MIT Yes Details →
4.0.2 23 Oct 2025 C1 MIT Yes Details →
4.0.1 22 Oct 2025 C1 MIT Yes Details →
4.0.0 22 Oct 2025 C1 MIT Yes Details →
4.0.0-beta.19 21 Oct 2025 none MIT — Details →
4.0.0-beta.18 15 Oct 2025 none MIT — Details →
4.0.0-beta.17 06 Oct 2025 none MIT — Details →
4.0.0-beta.16 03 Oct 2025 none MIT — Details →
4.0.0-beta.15 01 Oct 2025 none MIT — Details →
4.0.0-beta.14 01 Oct 2025 none MIT — Details →
4.0.0-beta.13 24 Sep 2025 none MIT — Details →
4.0.0-beta.12 22 Sep 2025 none MIT — Details →
4.0.0-beta.11 11 Sep 2025 none MIT — Details →
4.0.0-beta.10 01 Sep 2025 none MIT — Details →
4.0.0-beta.9 26 Aug 2025 none MIT — Details →
4.0.0-beta.8 12 Aug 2025 none MIT — Details →
4.0.0-beta.7 08 Aug 2025 none MIT — Details →
4.0.0-beta.6 04 Aug 2025 none MIT — Details →
4.0.0-beta.5 28 Jul 2025 none MIT — Details →
4.0.0-beta.4 22 Jul 2025 none MIT — Details →
4.0.0-beta.3 15 Jul 2025 none MIT — Details →
4.0.0-beta.2 24 Jun 2025 none MIT — Details →
4.0.0-beta.1 20 Jun 2025 none MIT — Details →
3.2.4 17 Jun 2025 none MIT — Details →
3.2.3 09 Jun 2025 none MIT — Details →
3.2.2 05 Jun 2025 none MIT — Details →
3.2.1 03 Jun 2025 none MIT — Details →
3.2.0 02 Jun 2025 none MIT — Details →
3.2.0-beta.3 28 May 2025 none MIT — Details →
3.1.4 19 May 2025 none MIT — Details →
3.2.0-beta.2 19 May 2025 none MIT — Details →
3.2.0-beta.1 05 May 2025 none MIT — Details →
3.1.3 05 May 2025 none MIT — Details →
3.1.2 21 Apr 2025 none MIT — Details →
3.1.1 31 Mar 2025 none MIT — Details →
3.1.0 31 Mar 2025 none MIT — Details →
3.1.0-beta.2 21 Mar 2025 none MIT — Details →
3.1.0-beta.1 17 Mar 2025 none MIT — Details →
3.0.9 17 Mar 2025 none MIT — Details →
3.0.8 06 Mar 2025 none MIT — Details →
3.0.7 24 Feb 2025 none MIT — Details →
3.0.6 18 Feb 2025 none MIT — Details →
3.0.5 03 Feb 2025 none MIT — Details →
2.1.9 03 Feb 2025 none MIT — Details →
1.6.1 03 Feb 2025 none MIT — Details →
3.0.4 23 Jan 2025 none — — Details →
3.0.3 21 Jan 2025 none — — Details →
3.0.2 17 Jan 2025 none — — Details →
3.0.1 16 Jan 2025 none — — Details →
3.0.0 16 Jan 2025 none — — Details →
3.0.0-beta.4 08 Jan 2025 none — — Details →
3.0.0-beta.3 20 Dec 2024 none — — Details →
3.0.0-beta.2 10 Dec 2024 none — — Details →
3.0.0-beta.1 05 Dec 2024 none — — Details →
2.1.8 02 Dec 2024 M1 — Yes Details →
2.1.7 02 Dec 2024 M1 — Yes Details →
2.1.6 26 Nov 2024 M1 — Yes Details →
2.2.0-beta.2 18 Nov 2024 none — — Details →
2.2.0-beta.1 13 Nov 2024 none — — Details →
2.1.5 13 Nov 2024 M1 — Yes Details →
2.1.4 28 Oct 2024 M1 — Yes Details →
2.1.3 14 Oct 2024 M1 — Yes Details →
2.1.2 02 Oct 2024 M1 — Yes Details →
2.1.1 13 Sep 2024 M1 — Yes Details →
2.1.0 12 Sep 2024 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for @vitest/browser

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-53633: Vitest Browser API Vulnerability Leading to Remote Code Execution 9.8 critical 5.0.0-beta.4 15 Jun 2026
CVE-2026-47428: Vitest Browser Mode XSS Vulnerability via Unvalidated otelCarrier Parameter 9.6 critical 4.1.6 01 Jun 2026
@vitest/browser: Critical File Access Bypass Vulnerability 9.4 critical 4.1.10 21 Jul 2026
CVE-2025-24963: @vitest/browser Arbitrary File Access Vulnerability 5.9 medium 2.1.9 04 Feb 2025

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 @vitest/browser

Is @vitest/browser safe to use?

Vulert records 4 vulnerabilities for @vitest/browser in npm: 3 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 @vitest/browser's Vulert package health score?

Vulert scores @vitest/browser 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 @vitest/browser affected?

No. 5.0.5, 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 @vitest/browser should I use?

5.0.5 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 @vitest/browser have?

4 vulnerabilities are recorded for @vitest/browser in the npm ecosystem: 3 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 @vitest/browser vulnerabilities disclosed?

3 vulnerabilities were recorded for @vitest/browser in the last 12 months, and the oldest entry in this database dates to 04 Feb 2025. 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 @vitest/browser 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 @vitest/browser for upcoming vulnerabilities?

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