Approved changes feed: RSS · Atom
cpe:2.3:a:sveltejs:devalue:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Sveltejs (01328e69-f2cf-539b-8c46-39ee16c7fd23) |
|---|---|
| Product | Devalue (7d3c5a45-bf42-5e46-a204-be0dad0d88b8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-92708 |
vulnerable | 2026-10-13 12:28:53.671716 |
devalue: Cross-request process memory disclosure in devalue when `stringify` / `uneval` serialize Node Buffers
HIGH (7.5)
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 rather than only the view, so serializing a Node Buffer, whose backing store is a process-wide shared pool, discloses up to 64 KB of unrelated process memory, including bytes from other in-flight requests. In a server-side-rendered framework such as SvelteKit or Nuxt, a public page whose load() returns a small Buffer, or that reads a small file, can therefore ship another user's request body or Authorization header in its HTML without authentication. Because this occurs during serialization, it fires on every such render and is not mitigated by the parse/unflatten prototype-pollution and denial-of-service guards, which only apply when parsing untrusted input. As a workaround, convert Node Buffer objects to Uint8Array before serialization. This issue has been fixed in version 5.9.3.
Published: 2026-09-18T19:54:28.335Z
Updated: 2026-09-23T19:38:36.551Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-81176 |
vulnerable | 2026-10-13 12:28:37.007358 |
Svelte devalue: DoS via malformed input
MEDIUM (5.3)
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 specially crafted untrusted payload can make the parser alternate between array representations, producing quadratic work as the payload grows and causing denial of service in applications that parse untrusted devalue data. This issue is fixed in version 5.9.2.
Published: 2026-09-16T18:34:34.881Z
Updated: 2026-09-17T19:25:51.846Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42570 |
vulnerable | 2026-07-29 00:49:32.070172 |
Svelte devalue: DoS via sparse array deserialization
HIGH (7.5)
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 much more memory than was needed when deserializing sparse arrays, leading to excessive memory consumption. This issue has been patched in version 5.8.1.
Published: 2026-06-09T16:12:26.377Z
Updated: 2026-08-24T12:07:13.887Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-30226 |
vulnerable | 2026-06-08 07:55:17.968539 |
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 payloads. Successful exploitation could lead to Denial of Service (DoS) or type confusion. This vulnerability is fixed in 5.6.4.
Published: 2026-03-11T17:47:40.016Z
Updated: 2026-03-12T13:51:34.208Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22775 |
vulnerable | 2026-06-08 07:51:13.805780 |
devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse
HIGH (7.5)
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 of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.
Published: 2026-01-15T18:59:37.499Z
Updated: 2026-07-15T01:19:19.060Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22774 |
vulnerable | 2026-06-08 07:51:13.804413 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-57820 |
vulnerable | 2026-06-08 07:33:16.175920 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.