Skip to content
OpenAdvisories

Vendor

sveltejs

48 known vulnerabilities.

sveltejs at a glance

Last 12 months
40
Critical · all time
0
Exploited · all time
0
Public exploit · all time
0
New vulnerabilities per month · last 12 months
0 5 10 December 2025: 0 vulnerabilities Dec 2025 January 2026: 4 vulnerabilities February 2026: 7 vulnerabilities March 2026: 1 vulnerability Mar April 2026: 2 vulnerabilities May 2026: 0 vulnerabilities June 2026: 4 vulnerabilities Jun July 2026: 0 vulnerabilities August 2026: 7 vulnerabilities September 2026: 2 vulnerabilities Sep October 2026: 4 vulnerabilities November 2026: 9 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202690
Oct 202640
Sep 202620
Aug 202670
Jul 202600
Jun 202640
May 202600
Apr 202620
Mar 202610
Feb 202670
Jan 202640
Dec 202500
Nov 202500
Oct 202500
Sep 202500
Aug 202510
Jul 202500
Jun 202500
May 202500
Apr 202510
Mar 202500
Feb 202500
Jan 202500
Dec 202400

48 results · Feed

  • High 7.5

    Devalue before 5.6.3 Denial of Service via Sparse Array Serialization

    The devalue package for npm before 5.6.3 can consume excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who manages to get a sparse array created on the server, which mainstream wire formats do not allow, and seriali…

  • Medium 4.4

    Sveltejs devalue before 5.6.3 Prototype Pollution via uneval Output

    Sveltejs devalue before 5.6.3 contains a prototype pollution vulnerability that allows attackers to alter object prototypes by supplying untrusted data to uneval. When the generated code is later evaluated, it creates objects with polluted prototypes, produci…

  • Low 3.7

    Sveltejs devalue before 5.6.4 Prototype Injection via parse and unflatten

    Sveltejs devalue before 5.6.4 contains a prototype injection vulnerability that allows attackers to inject __proto__ own properties into objects returned by devalue.parse and devalue.unflatten. Attackers can supply crafted serialized input that, when downstre…

  • High 7.5

    Devalue before 5.9.3 CPU Amplification Denial of Service via uneval

    Sveltejs devalue before 5.9.3 contains a denial of service vulnerability that allows attackers to cause CPU amplification by supplying sparse arrays to uneval. Attackers who influence sparse values passed to uneval can force synchronous work proportional to t…

  • High 7.5

    Devalue before 5.9.3 Quadratic Expansion Denial of Service via uneval

    Sveltejs devalue before 5.9.3 contains a resource exhaustion vulnerability where repeated primitive strings cause quadratic expansion in the uneval function. Attackers can supply a small crafted payload that is parsed and then passed to uneval, producing a ve…

  • High 7.5

    Sveltejs devalue before 5.9.3 Memory Exhaustion via uneval Sparse Arrays

    Sveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array ser…

  • High 7.5

    Devalue before 5.9.3 Typed-Array Allocation Validation Bypass via parse

    Devalue before 5.9.3 contains a validation bypass vulnerability that allows custom ArrayBuffer revivers to skip typed-array allocation checks in the parse function. Attackers can supply very small crafted input processed by a malformed ArrayBuffer reviver to …

  • High 7.5

    Devalue 5.8.0 before 5.9.3 Denial of Service via stringifyAsync Unhandled Rejection

    devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller cat…

  • Low 3.7

    Sveltejs devalue before 5.9.3 __proto__ Rejection Bypass via Property-Key Coercion

    devalue before 5.9.3 allows malformed null-prototype object keys to bypass parse's __proto__ rejection through property-key coercion, an incomplete fix for GHSA-mwv9-gp5h-frr4. Attackers can supply crafted payloads that yield objects with a __proto__ own prop…

  • Medium 5.3

    SvelteKit before 3.0.0 SSRF via Redirects in Server-Side Self-Fetch Fallbacks

    SvelteKit before 3.0.0 contains a server-side request forgery vulnerability that allows remote attackers to reach internal services because self-fetch fallbacks follow HTTP redirects automatically. Attackers can manipulate the Host or forwarded headers to poi…

  • High 7.5

    SvelteKit 2.10.0 before 3.0.0 Path Traversal via vite preview on Windows

    SvelteKit (@sveltejs/kit) from 2.10.0 before 3.0.0 contains a path traversal vulnerability in the vite preview server on Windows that allows unauthenticated attackers to read files outside the prerendered output directory. Attackers who can reach the preview …

  • Medium 4.7

    SvelteKit before 3.0.0 XSS via Cache-Control Header in Prerendered Pages

    SvelteKit (@sveltejs/kit) before 3.0.0 contains a cross-site scripting vulnerability in prerendered pages because a cache-control header value set via setHeaders is inserted without escaping into a <meta http-equiv="cache-control"> tag. An attacker who can in…

  • Medium 4.7

    SvelteKit before 3.0.0 Open Redirect via Enhanced Form Actions

    SvelteKit (@sveltejs/kit) before 3.0.0 contains an open redirect vulnerability in enhanced form actions (use:enhance) on routes accepting paths beginning with a double slash. Attackers can craft action paths starting with // that become protocol-relative URLs…

  • High 7.5

    devalue: Cross-request process memory disclosure in devalue when `stringify` / `uneval` serialize Node Buffers

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. In versions 5.1.0 through 5.9.2, stringify and uneval functions serialize a typed array by emitting its entire backing ArrayBuffer rat…

  • Medium 5.3

    Svelte devalue: DoS via malformed input

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. Prior to 5.9.2, devalue.parse does not reject out-of-bounds indices that are greater than or equal to values.length in src/parse.js. A…

  • High 7.5

    SvelteKit before 2.52.2 CPU Exhaustion via Remote Form Deserialization

    SvelteKit (@sveltejs/kit) versions >=2.49.0 and <=2.52.1 with experimental remote functions and form enabled contain a CPU exhaustion vulnerability in form deserialization. An attacker can send malformed form data to cause the server to become unresponsive wh…

  • High 7.5

    SvelteKit before 2.52.2 Memory Exhaustion via Remote Form Deserialization

    SvelteKit (@sveltejs/kit) versions >=2.49.0 and <=2.52.1 with experimental remote functions (experimental.remoteFunctions) and form enabled contain a memory exhaustion vulnerability in remote form deserialization. Malformed form data can cause excessive memor…

  • Medium 5.9

    SvelteKit 2.38.0 before 2.60.1 Cross-User Data Disclosure via query.batch

    SvelteKit versions from 2.38.0 before 2.60.1 contain a race condition in query.batch that allows concurrent requests from different users to merge under a single request context. Attackers can exploit specific timing conditions to access sensitive data from o…

  • High 7.5

    SvelteKit 2.49.0 before 2.53.3 Denial of Service via form

    SvelteKit versions from 2.49.0 through 2.53.2 (fixed in 2.53.3) contain a deserialization expansion issue in the experimental form remote function. When an application enables experimental.remoteFunctions and uses the form function to process the files array …

  • Medium 4.3

    SvelteKit before 2.69.1 Prototype Pollution via File Input

    SvelteKit versions before 2.69.1 contain a prototype pollution vulnerability in remote form functions with file input fields that accept arbitrary user-controlled path names. Attackers can manipulate the deletion path to remove methods on the prototype, poten…

  • Medium 5.3

    SvelteKit before 2.69.1 Denial of Service via Remote Form

    SvelteKit before 2.69.1 fails to properly validate remote form function payload sizes, allowing attackers to crash the Node process by sending large payloads. Repeated exploitation causes denial of service by repeatedly crashing the application process.

  • Medium 5.3

    SvelteKit: ReDoS (O(n^2)) in content negotiation — unauthenticated DoS via the Accept header

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.70.2, the content negotiation header parser used by SvelteKit's request handling (for headers such as Accept) uses a regular expression vulnerable to …

  • Medium 5.1

    Cross-site scripting via spread attributes in Svelte SSR

    Svelte is a performance oriented web framework. Prior to version 5.55.7, when using spread syntax to render attributes from untrusted data, event handler properties are included in the rendered HTML output. If an application spreads user-controlled or externa…

  • Medium 5.9

    Svelte: ReDoS in `<svelte:element>` Tag Validation

    Svelte is a performance oriented web framework. From version 5.51.5 to before version 5.55.7, an internal regex in the Svelte runtime can take exponential time to test in <svelte:element this={tag}></svelte:element>. This issue has been patched in version 5.5…

  • Medium 5.3

    Svelte: XSS via DOM Clobbering of Internal Framework State

    Svelte is a performance oriented web framework. Prior to version 5.55.7, Svelte was vulnerable to DOM clobbering of its internal framework state on elements, potentially leading to XSS attacks. This issue has been patched in version 5.55.7.

  • High 7.5

    Svelte devalue: DoS via sparse array deserialization

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From version 5.6.3 to before version 5.8.1, devalue.parse could, due to quirks in some JavaScript engines, be convinced to allocate mu…

  • Medium 6.3

    SvelteKit's invalidated redirect in handle hook causes Denial-of-Service

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.57.1, redirect, when called from inside the handle server hook with a location parameter containing characters that are invalid in a HTTP header, will…

  • High 8.2

    SvelteKit has a BODY_SIZE_LIMIT bypass in @sveltejs/adapter-node

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.57.1, under certain circumstances, requests could bypass the BODY_SIZE_LIMIT on SvelteKit applications running with adapter-node. This bypass does not…

  • Medium 6.3

    devalue has prototype pollution in devalue.parse and devalue.unflatten

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. In devalue v5.6.3 and earlier, devalue.parse and devalue.unflatten were susceptible to prototype pollution via maliciously crafted pay…

  • Medium 5.3

    Svelte Vulnerable to XSS via HTML Comment Injection in SSR Error Boundary Hydration Markers

    Svelte performance oriented web framework. Prior to version 5.53.5, errors from `transformError` were not correctly escaped prior to being embedded in the HTML output, causing potential HTML injection and XSS if attacker-controlled content is returned from `t…

  • Medium 5.3

    Svelte vulnerable to XSS during SSR with contenteditable `bind:innerText` and `bind:textContent`

    Svelte performance oriented web framework. Prior to version 5.53.5, the contents of `bind:innerText` and `bind:textContent` on `contenteditable` elements were not properly escaped. This could enable HTML injection and Cross-Site Scripting (XSS) if rendering u…

  • Medium 5.3

    Svelte SSR attribute spreading includes inherited properties from prototype chain

    svelte performance oriented web framework. Prior to 5.51.5, in server-side rendering, attribute spreading on elements (e.g. <div {...attrs}>) enumerates inherited properties from the object's prototype chain rather than only own properties. In environments wh…

  • Medium 5.1

    Svelte SSR does not validate dynamic element tag names in `<svelte:element>`

    svelte performance oriented web framework. Prior to 5.51.5, when using <svelte:element this={tag}> in server-side rendering, the provided tag name is not validated or sanitized before being emitted into the HTML output. If the tag string contains unexpected c…

  • Medium 5.1

    Svelte affected by cross-site scripting via spread attributes in Svelte SSR

    svelte performance oriented web framework. Versions of svelte prior to 5.51.5 are vulnerable to cross-site scripting (XSS) during server-side rendering. When using spread syntax to render attributes from untrusted data, event handler properties are included i…

  • Medium 5.1

    Svelte affected by XSS in SSR `<option>` element

    svelte performance oriented web framework. From 5.39.3, <=5.51.4, in certain circumstances, the server-side rendering output of an <option> element does not properly escape its content, potentially allowing HTML injection in the SSR output. Client-side render…

  • Medium 5.3

    Cache poisoning in @sveltejs/adapter-vercel

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Versions of @sveltejs/adapter-vercel prior to 6.3.2 are vulnerable to cache poisoning. An internal query parameter intended for Incremental Static Regeneration (…

  • High 7.5

    devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.1.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial…

  • High 7.5

    devalue vulnerable to denial of service due to memory exhaustion in devalue.parse

    Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial…

  • High 8.2

    SvelteKit has a memory amplification DoS in Remote Functions binary form deserializer

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From 2.49.0 to 2.49.4, the experimental form remote function uses a binary data format containing a representation of submitted form data. A specially-crafted pa…

  • High 8.4

    SvelteKit Denial of service and possible SSRF when using prerendering

    SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.49.5, SvelteKit is vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions. From 2.44.0 through 2.49.4…