Intel

AIKIDO-2026-505358

devalue is vulnerable to Information Disclosure

CVE-2026-92708Published Sep 23, 2026
September 23, 2026

75

CVE Score

High

Information Disclosure

Are you affected? Scan for Free

TL;DR

stringify, stringifyAsync, and uneval serialize a typed array or Node Buffer by copying its full backing ArrayBuffer instead of only the bytes the view exposes. A Node Buffer's backing store is Node's shared allocation pool for the whole process, so serializing even a small Buffer copies unrelated bytes from other requests into the output. In an SSR framework, a page whose load() returns a small Buffer or a small file read can leak another request's body or Authorization header into its rendered HTML. The fix copies only the visible bytes into a fresh buffer before serializing.

How do I fix this?

Upgrade the devalue library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you serialize a Node Buffer value with stringify, stringifyAsync, or uneval.

Package

Versions

5.1.0 - 5.9.2

Fixed in 5.9.3

Background info

devalue is vulnerable to Information Disclosure in versions 5.1.0 - 5.9.2.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea