VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@sveltejs/kit: vulnerability history, versions and safety

@sveltejs/kit is a package in the npm ecosystem. Vulert records 17 vulnerabilities for it across 84 releases, from Apr 2023 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded H6 M8 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
11 in the last 12 months

Most recent disclosure 07 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @sveltejs/kit vulnerabilities

Vulert verdict on @sveltejs/kit 3.1.0 i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 17 over 3 years · 11 in the last year i
  • Latest disclosure 07 Aug 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 12 packages i
  • Stars 20,863 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 @sveltejs/kit, 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
3.1.0 14 Oct 2026 none MIT — Details →
3.0.1 06 Oct 2026 none MIT — Details →
3.0.0 01 Oct 2026 none MIT — Details →
3.0.0-next.32 01 Oct 2026 none MIT — Details →
3.0.0-next.31 30 Sep 2026 none MIT — Details →
3.0.0-next.30 27 Sep 2026 none MIT — Details →
3.0.0-next.29 25 Sep 2026 none MIT — Details →
3.0.0-next.28 24 Sep 2026 none MIT — Details →
3.0.0-next.27 08 Sep 2026 none MIT — Details →
3.0.0-next.25 21 Aug 2026 none MIT — Details →
3.0.0-next.24 20 Aug 2026 none MIT — Details →
2.70.3 18 Aug 2026 none MIT — Details →
3.0.0-next.23 13 Aug 2026 none MIT — Details →
3.0.0-next.22 13 Aug 2026 none MIT — Details →
3.0.0-next.21 12 Aug 2026 none MIT — Details →
3.0.0-next.20 11 Aug 2026 none MIT — Details →
3.0.0-next.19 11 Aug 2026 none MIT — Details →
3.0.0-next.18 10 Aug 2026 none MIT — Details →
3.0.0-next.17 10 Aug 2026 none MIT — Details →
3.0.0-next.15 07 Aug 2026 none MIT — Details →
3.0.0-next.16 07 Aug 2026 none MIT — Details →
3.0.0-next.14 04 Aug 2026 none MIT — Details →
2.70.2 29 Jul 2026 none MIT — Details →
3.0.0-next.13 29 Jul 2026 none MIT — Details →
3.0.0-next.12 24 Jul 2026 none MIT — Details →
3.0.0-next.11 20 Jul 2026 none MIT — Details →
2.70.1 19 Jul 2026 M1 MIT Yes Details →
3.0.0-next.10 18 Jul 2026 none MIT — Details →
3.0.0-next.9 17 Jul 2026 none MIT — Details →
2.70.0 17 Jul 2026 M1 MIT Yes Details →
3.0.0-next.8 14 Jul 2026 none MIT — Details →
2.69.3 13 Jul 2026 M1 MIT Yes Details →
3.0.0-next.7 08 Jul 2026 none MIT — Details →
2.69.2 08 Jul 2026 M1 MIT Yes Details →
2.69.1 02 Jul 2026 M1 MIT Yes Details →
3.0.0-next.6 02 Jul 2026 none MIT — Details →
2.69.0 01 Jul 2026 M3 MIT Yes Details →
2.68.0 24 Jun 2026 M3 MIT Yes Details →
2.67.0 22 Jun 2026 M3 MIT Yes Details →
2.66.0 18 Jun 2026 M3 MIT Yes Details →
2.65.2 16 Jun 2026 M3 MIT Yes Details →
2.65.1 14 Jun 2026 M3 MIT Yes Details →
3.0.0-next.4 11 Jun 2026 none MIT — Details →
3.0.0-next.3 11 Jun 2026 none MIT — Details →
2.65.0 11 Jun 2026 M3 MIT Yes Details →
3.0.0-next.2 08 Jun 2026 none MIT — Details →
2.64.0 08 Jun 2026 M3 MIT Yes Details →
2.63.1 08 Jun 2026 M3 MIT Yes Details →
3.0.0-next.1 05 Jun 2026 none MIT — Details →
3.0.0-next.0 05 Jun 2026 none MIT — Details →
2.63.0 04 Jun 2026 M3 MIT Yes Details →
2.62.0 02 Jun 2026 M3 MIT Yes Details →
2.61.1 24 May 2026 M3 MIT Yes Details →
2.61.0 22 May 2026 M3 MIT Yes Details →
2.60.1 14 May 2026 M3 MIT Yes Details →
2.60.0 14 May 2026 M4 MIT Yes Details →
2.59.1 05 May 2026 M4 MIT Yes Details →
2.59.0 01 May 2026 M4 MIT Yes Details →
2.58.0 23 Apr 2026 M4 MIT Yes Details →
2.57.1 09 Apr 2026 M4 MIT Yes Details →
2.57.0 08 Apr 2026 H1 M5 MIT Yes Details →
2.56.1 03 Apr 2026 H1 M5 MIT Yes Details →
2.56.0 03 Apr 2026 H1 M5 MIT Yes Details →
2.55.0 12 Mar 2026 H1 M5 MIT Yes Details →
2.54.0 11 Mar 2026 H1 M5 MIT Yes Details →
2.53.4 28 Feb 2026 H1 M5 MIT Yes Details →
2.53.3 26 Feb 2026 H1 M5 MIT Yes Details →
2.53.2 25 Feb 2026 H1 M5 L1 MIT Yes Details →
2.53.1 24 Feb 2026 H1 M5 L1 MIT Yes Details →
2.53.0 20 Feb 2026 H1 M5 L1 MIT Yes Details →
2.52.2 18 Feb 2026 H1 M5 L1 MIT Yes Details →
2.52.0 15 Feb 2026 H1 M7 L1 MIT Yes Details →
2.51.0 12 Feb 2026 H1 M7 L1 MIT Yes Details →
2.50.2 02 Feb 2026 H1 M7 L1 MIT Yes Details →
2.50.1 23 Jan 2026 H1 M7 L1 MIT Yes Details →
2.50.0 17 Jan 2026 H1 M7 L1 MIT Yes Details →
2.49.5 15 Jan 2026 H1 M7 L1 MIT Yes Details →
2.49.4 09 Jan 2026 H3 M7 L1 MIT Yes Details →
2.49.3 05 Jan 2026 H3 M7 L1 MIT Yes Details →
2.49.2 08 Dec 2025 H3 M7 L1 MIT Yes Details →
2.49.1 02 Dec 2025 H3 M7 L1 MIT Yes Details →
2.49.0 20 Nov 2025 H3 M7 L1 MIT Yes Details →
2.48.8 20 Nov 2025 H2 M5 MIT Yes Details →
2.48.7 20 Nov 2025 H2 M5 MIT Yes Details →
2.48.6 20 Nov 2025 H2 M5 MIT Yes Details →
2.48.5 14 Nov 2025 H2 M5 MIT Yes Details →
2.48.4 30 Oct 2025 H2 M5 MIT Yes Details →
2.48.3 29 Oct 2025 H2 M5 MIT Yes Details →
2.48.2 28 Oct 2025 H2 M5 MIT Yes Details →
2.48.1 28 Oct 2025 H2 M5 MIT Yes Details →
2.48.0 26 Oct 2025 H2 M5 MIT Yes Details →
2.47.3 22 Oct 2025 H2 M5 MIT Yes Details →
2.47.2 20 Oct 2025 H2 M5 MIT Yes Details →
2.47.1 17 Oct 2025 H2 M5 MIT Yes Details →
2.47.0 15 Oct 2025 H2 M5 MIT Yes Details →
2.46.5 13 Oct 2025 H2 M5 MIT Yes Details →
2.46.4 08 Oct 2025 H2 M5 MIT Yes Details →
2.46.3 08 Oct 2025 H2 M5 MIT Yes Details →
2.46.2 07 Oct 2025 H2 M5 MIT Yes Details →
2.46.1 07 Oct 2025 H2 M5 MIT Yes Details →
2.46.0 07 Oct 2025 H2 M5 — Yes Details →
2.45.0 07 Oct 2025 H2 M5 — Yes Details →
2.44.0 05 Oct 2025 H2 M5 — Yes Details →
2.43.8 03 Oct 2025 H2 M5 — Yes Details →
2.43.7 01 Oct 2025 H2 M5 — Yes Details →
2.43.6 30 Sep 2025 H2 M5 — Yes Details →
2.43.5 25 Sep 2025 H2 M5 — Yes Details →
2.43.4 24 Sep 2025 H2 M5 — Yes Details →
2.43.3 24 Sep 2025 H2 M5 — Yes Details →
2.43.2 23 Sep 2025 H2 M5 — Yes Details →
2.43.1 22 Sep 2025 H2 M5 — Yes Details →
2.43.0 22 Sep 2025 H2 M5 — Yes Details →
2.42.2 18 Sep 2025 H2 M5 — Yes Details →
2.42.1 16 Sep 2025 H2 M5 — Yes Details →
2.42.0 16 Sep 2025 H2 M5 — Yes Details →
2.41.0 16 Sep 2025 H2 M5 — Yes Details →
2.40.0 15 Sep 2025 H2 M5 — Yes Details →
2.39.1 12 Sep 2025 H2 M5 — Yes Details →
2.39.0 12 Sep 2025 H2 M5 — Yes Details →
2.38.1 11 Sep 2025 H2 M5 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 3
  • 2025 1
  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for @sveltejs/kit

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-29003: SvelteKit Cross-Site Request Forgery Vulnerability 8.8 high 1.15.1 04 Apr 2023
CVE-2023-29008: SvelteKit Insufficient CSRF Protection for CORS Requests 8.8 high 1.15.2 07 Apr 2023
CVE-2025-67647: SvelteKit Denial of Service and SSRF Vulnerability in Prerendering 8.4 high 2.49.5 15 Jan 2026
CVE-2026-22803: @sveltejs/kit Memory Amplification DoS Vulnerability in Remote Functions 8.2 high 2.49.5 15 Jan 2026
CVE-2026-40073: @sveltejs/adapter-node BODY_SIZE_LIMIT Bypass Vulnerability 8.2 high 2.57.1 10 Apr 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 @sveltejs/kit

Is @sveltejs/kit safe to use?

Vulert records 17 vulnerabilities for @sveltejs/kit in npm: 0 critical, 6 high, 8 medium and 3 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 @sveltejs/kit's Vulert package health score?

Vulert scores @sveltejs/kit 66/100, which reads as usable, but worth attention. 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 @sveltejs/kit affected?

No. 3.1.0, 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 @sveltejs/kit have?

17 vulnerabilities are recorded for @sveltejs/kit in the npm ecosystem: 0 critical, 6 high, 8 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @sveltejs/kit vulnerabilities disclosed?

11 vulnerabilities were recorded for @sveltejs/kit in the last 12 months, and the oldest entry in this database dates to 04 Apr 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 @sveltejs/kit 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 @sveltejs/kit for upcoming vulnerabilities?

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