Sign in
Deutsch English Español Polski
High

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

  • Disclosed: 15.01.2026
  • Updated: 11.10.2026 10:22

Summary

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.

Details

The parser's ArrayBuffer hydration logic does not properly validate input before processing. Specially crafted inputs can cause disproportionate memory allocation or CPU usage on the receiving system.

Impact

This is a denial of service vulnerability affecting systems that use devalue.parse to handle data from potentially untrusted sources.

Affected systems should upgrade to patched versions immediately.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package devalue >= 5.1.0, < 5.6.2 5.6.2

References

CVSS score 7.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-405
Platform
npm
Package
devalue
Disclosed
15.01.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-g2pg-6438-jwpf - CC BY 4.0

Vulnerability history: devalue

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (16) in the archive
Total entries
16
First → latest
08.2025 10.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 8
  • Medium 4
  • Low 4

Disclosures per year

Severity:
  1. devalue: `stringify`/`uneval` serialize shared memory
    High · 7.5 CVE-2026-92708 >= 5.1.0, < 5.9.3 5.9.3
  2. devalue: Repeated primitive strings cause quadratic expansion in uneval
    High ghsa-mcm9-63f2-9j32 < 5.9.3 5.9.3
  3. devalue: Custom ArrayBuffer revivers can bypass typed-array allocation validation
    High ghsa-r9w8-h9r3-54w4 < 5.9.3 5.9.3
  4. devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise
    High ghsa-x5rw-q4pp-hg5g >= 5.8.0, < 5.9.3 5.9.3
  5. Svelte devalue: DoS via sparse array deserialization
    High · 7.5 CVE-2026-42570 >= 5.6.3, < 5.8.1 5.8.1
  6. devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse this entry
    High · 7.5 CVE-2026-22775 >= 5.1.0, < 5.6.2 5.6.2
  7. Devalue is vulnerable to denial of service due to memory exhaustion in devalue.parse
    High · 7.5 CVE-2026-22774 >= 5.3.0, < 5.6.2 5.6.2
  8. devalue prototype pollution vulnerability
    High CVE-2025-57820 < 5.3.2 5.3.2

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.