CVE-2026-92708

published 18 Sep 2026 · updated 23 Sep 2026

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

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
sveltejs>=5.1.0 <5.9.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92708 severity on Zeptric[![CVE-2026-92708](https://zeptric.io/badge/cve/CVE-2026-92708.svg)](https://zeptric.io/cve/CVE-2026-92708)