Sensitive Information in Resource Not Removed Before Reuse Affecting devalue package, versions >=5.1.0 <5.9.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-DEVALUE-20044498
- published22 Sept 2026
- disclosed18 Sept 2026
- creditJuan Lipez
Introduced: 18 Sep 2026
NewCVE-2026-92708 (opens in a new tab)How to fix?
Upgrade devalue to version 5.9.3 or higher.
Overview
devalue is a JSON.stringify, but handles cyclical references, repeated references, undefined, regular expressions, dates, Map and Set.
Affected versions of this package are vulnerable to Sensitive Information in Resource Not Removed Before Reuse via the viewInfo operation in src/operations.js and the typed-array serialization path in src/uneval.js, when a Node.js Buffer is serialized. Node Buffer instances are backed by a shared memory pool that may contain unrelated, sensitive data beyond the visible bytes of the buffer. Because the library previously serialized the full backing ArrayBuffer rather than only the bytes visible through the Buffer view, an attacker who can influence what gets serialized (for example, during SSR rendering) can cause the full pool contents - including data from other allocations - to be included in the serialized output and exposed to the client.