Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.3

Underscore.js can cause a server crash with malicious data

UBUNTU-CVE-2026-27601
Summary

Prior to version 1.13.8, the _.flatten and _.isEqual functions in Underscore.js can be exploited by an attacker to make the server run out of memory and crash. This can happen if the attacker sends a specially crafted data structure that causes the functions to use up all the available memory. To fix this issue, update to version 1.13.8 or later. If you're using an earlier version, you should limit the depth of the data structure being passed to these functions.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software
VendorProductAffected versionsFix available
canonical ruby-rails-assets-underscore All versions
canonical ruby-rails-assets-underscore All versions
canonical ruby-rails-assets-underscore All versions
canonical ruby-rails-assets-underscore All versions
Original title
Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, a...
Original description
Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.
osv CVSS4.0 8.3
osv CVSS3.1 7.5
Published: 3 Mar 2026 · Updated: 13 Mar 2026 · First seen: 9 Mar 2026