Underscore.js has unlimited recursion in _.flatten and _.isEqual, potential for DoS attack
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-27601
PublishedUnderscore.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.
- Source published
- 3 Mar 2026 22:38:38 UTC
- Source modified
- 4 Mar 2026 16:44:40 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
euvd · EUVD-2026-9341
PublishedUnderscore.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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 3, 2026, 10:38:38 PM
dateUpdated: Mar 4, 2026, 4:44:40 PM
15 related source bulletins · separate from aliases
openSUSE-SU-2026:10424-1: jupyter-bqplot-jupyterlab-0.5.46-14.1 on GA media
CVE-2026-25547 · CVE-2026-27601
WID-SEC-W-2026-1220: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2026-26278 · CVE-2026-27601 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-29786 · CVE-2026-30827 · CVE-2026-31802 · CVE-2026-31988 · CVE-2026-32141 · CVE-2026-33036 · CVE-2026-33228
WID-SEC-W-2026-4090: Oracle Communications: Mehrere Schwachstellen
CVE-2021-42576 · CVE-2024-38356 · CVE-2024-47072 · CVE-2024-6763 · CVE-2025-13151 · CVE-2025-48734 · CVE-2025-48924 · CVE-2026-10050 · CVE-2026-101603 · CVE-2026-101604 · CVE-2026-101606 · CVE-2026-101680 · CVE-2026-101758 · CVE-2026-101759 · CVE-2026-101763 · CVE-2026-101764 · CVE-2026-101765 · CVE-2026-101790 · CVE-2026-101791 · CVE-2026-101792 · CVE-2026-101793 · CVE-2026-101807 · CVE-2026-13221 · CVE-2026-13321 · CVE-2026-21441 · CVE-2026-21716 · CVE-2026-22702 · CVE-2026-27601 · CVE-2026-28369 · CVE-2026-29167 · CVE-2026-32327 · CVE-2026-34481 · CVE-2026-34487 · CVE-2026-39892 · CVE-2026-41001 · CVE-2026-41855 · CVE-2026-41989 · CVE-2026-45292 · CVE-2026-4800 · CVE-2026-49844 · CVE-2026-54291 · CVE-2026-54369 · CVE-2026-54399 · CVE-2026-5450 · CVE-2026-54512 · CVE-2026-54874 · CVE-2026-54906 · CVE-2026-55831 · CVE-2026-55858 · CVE-2026-55956 · CVE-2026-55971 · CVE-2026-56130 · CVE-2026-56740 · CVE-2026-5704 · CVE-2026-5795 · CVE-2026-58014 · CVE-2026-58016 · CVE-2026-58389 · CVE-2026-5928 · CVE-2026-59889 · CVE-2026-59901 · CVE-2026-59949 · CVE-2026-60075 · CVE-2026-61674 · CVE-2026-63388 · CVE-2026-63639 · CVE-2026-64193 · CVE-2026-6653 · CVE-2026-68494 · CVE-2026-68497 · CVE-2026-68525 · CVE-2026-69247 · CVE-2026-7168 · CVE-2026-75595 · CVE-2026-75596 · CVE-2026-78030 · CVE-2026-83406 · CVE-2026-84939 · CVE-2026-86219 · CVE-2026-8643 · CVE-2026-87297 · CVE-2026-8763 · CVE-2026-91612 · CVE-2026-91613 · CVE-2026-91614 · CVE-2026-91627 · CVE-2026-91628 · CVE-2026-91629
WID-SEC-W-2026-2438: Oracle Commerce: Mehrere Schwachstellen
CVE-2025-14017 · CVE-2025-48976 · CVE-2025-68161 · CVE-2026-27601 · CVE-2026-34316 · CVE-2026-34487 · CVE-2026-4176 · CVE-2026-42403 · CVE-2026-42587 · CVE-2026-61129 · CVE-2026-61130 · CVE-2026-61131 · CVE-2026-61132 · CVE-2026-61133 · CVE-2026-61134 · CVE-2026-61135 · CVE-2026-61136 · CVE-2026-61137 · CVE-2026-61145 · CVE-2026-61146 · CVE-2026-61147 · CVE-2026-61148 · CVE-2026-61149 · CVE-2026-61150 · CVE-2026-61151 · CVE-2026-61152 · CVE-2026-61153 · CVE-2026-61154 · CVE-2026-61155 · CVE-2026-61156 · CVE-2026-61157 · CVE-2026-61158 · CVE-2026-61159 · CVE-2026-61160 · CVE-2026-61161 · CVE-2026-61162 · CVE-2026-61163 · CVE-2026-61164 · CVE-2026-61165
msrc_CVE-2026-27601: Underscore.js has unlimited recursion in _.flatten and _.isEqual, potential for DoS attack
CVE-2026-27601
RHSA-2026:13826: Red Hat Security Advisory: Red Hat Developer Hub 1.9.4 release.
CVE-2025-62718 · CVE-2025-69534 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-3118 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-27601 · CVE-2026-27904 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-29186 · CVE-2026-32141 · CVE-2026-32280 · CVE-2026-32282 · CVE-2026-33228 · CVE-2026-33891 · CVE-2026-33894 · CVE-2026-33895 · CVE-2026-33896 · CVE-2026-39983 · CVE-2026-40175 · CVE-2026-40895
openSUSE-SU-2026:10427-1: jupyter-matplotlib-0.11.7-17.1 on GA media
CVE-2026-27601
RHSA-2026:24841: Red Hat Security Advisory: Red Hat Developer Hub 1.10.0 release.
CVE-2026-2950 · CVE-2026-4923 · CVE-2026-22036 · CVE-2026-27601 · CVE-2026-31988 · CVE-2026-32235 · CVE-2026-33349
NCSC-2026-0325: Kwetsbaarheden verholpen in Atlassian producten
CVE-2021-44906 · CVE-2022-3517 · CVE-2023-45133 · CVE-2025-14813 · CVE-2026-0603 · CVE-2026-2332 · CVE-2026-3505 · CVE-2026-4800 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-10050 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13149 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-24734 · CVE-2026-25639 · CVE-2026-27601 · CVE-2026-27606 · CVE-2026-29786 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41284 · CVE-2026-41842 · CVE-2026-41845 · CVE-2026-41850 · CVE-2026-41851 · CVE-2026-41907 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42041 · CVE-2026-42198 · CVE-2026-42583 · CVE-2026-42587 · CVE-2026-43513 · CVE-2026-44249 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44490 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-47838 · CVE-2026-48043 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53434 · CVE-2026-54291 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55685 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59869 · CVE-2026-59871 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69192
WID-SEC-W-2026-2923: Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye, und Jira): Mehrere Schwachstellen
CVE-2019-13990 · CVE-2021-44906 · CVE-2022-1471 · CVE-2022-23521 · CVE-2022-3517 · CVE-2022-41903 · CVE-2023-22518 · CVE-2023-22522 · CVE-2023-22523 · CVE-2023-22524 · CVE-2023-22527 · CVE-2023-45133 · CVE-2023-46604 · CVE-2025-14813 · CVE-2026-0603 · CVE-2026-10050 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13149 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-2332 · CVE-2026-24734 · CVE-2026-25639 · CVE-2026-27601 · CVE-2026-27606 · CVE-2026-29786 · CVE-2026-3505 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41284 · CVE-2026-41842 · CVE-2026-41845 · CVE-2026-41850 · CVE-2026-41851 · CVE-2026-41907 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42041 · CVE-2026-42198 · CVE-2026-42583 · CVE-2026-42587 · CVE-2026-43513 · CVE-2026-44249 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44490 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-47838 · CVE-2026-4800 · CVE-2026-48043 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53434 · CVE-2026-54291 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55685 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59869 · CVE-2026-59871 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69192
openSUSE-SU-2026:12070-1: velociraptor-0.76.7.0.git145.b60ef1146-1.1 on GA media
CVE-2025-0914 · CVE-2026-12143 · CVE-2026-14257 · CVE-2026-17535 · CVE-2026-18348 · CVE-2026-18636 · CVE-2026-18638 · CVE-2026-18639 · CVE-2026-18860 · CVE-2026-27601 · CVE-2026-29074 · CVE-2026-41650 · CVE-2026-45623 · CVE-2026-49356 · CVE-2026-5329 · CVE-2026-53550 · CVE-2026-55602 · CVE-2026-56852 · CVE-2026-59869 · CVE-2026-6290 · CVE-2026-64951 · CVE-2026-64952 · CVE-2026-64954 · CVE-2026-65903 · CVE-2026-65912 · CVE-2026-65913 · CVE-2026-65914 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-6863 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-6948 · CVE-2026-73086 · CVE-2026-73646 · CVE-2026-73650 · CVE-2026-7572 · CVE-2026-7573 · CVE-2026-84369 · CVE-2026-84370
openSUSE-SU-2026:10440-1: jupyter-nbclassic-1.3.3-1.1 on GA media
CVE-2026-27601
openSUSE-SU-2026:21448-1: Security update for agama-web-ui
CVE-2025-7783 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13311 · CVE-2026-13676 · CVE-2026-27601 · CVE-2026-40181 · CVE-2026-49356 · CVE-2026-53550 · CVE-2026-53632 · CVE-2026-54466 · CVE-2026-54490 · CVE-2026-55602
WID-SEC-W-2026-2437: Oracle Communications: Mehrere Schwachstellen
CVE-2025-13151 · CVE-2025-14017 · CVE-2025-14087 · CVE-2025-14821 · CVE-2025-31651 · CVE-2025-32990 · CVE-2025-5318 · CVE-2025-64713 · CVE-2025-6491 · CVE-2025-66418 · CVE-2025-70873 · CVE-2025-8837 · CVE-2025-9900 · CVE-2026-0861 · CVE-2026-21441 · CVE-2026-22747 · CVE-2026-2332 · CVE-2026-23865 · CVE-2026-23903 · CVE-2026-24051 · CVE-2026-24400 · CVE-2026-27099 · CVE-2026-27135 · CVE-2026-27141 · CVE-2026-27601 · CVE-2026-28390 · CVE-2026-29167 · CVE-2026-30922 · CVE-2026-31431 · CVE-2026-31790 · CVE-2026-33557 · CVE-2026-34478 · CVE-2026-34480 · CVE-2026-34481 · CVE-2026-34487 · CVE-2026-34500 · CVE-2026-34520 · CVE-2026-39892 · CVE-2026-40192 · CVE-2026-40976 · CVE-2026-4111 · CVE-2026-4176 · CVE-2026-41855 · CVE-2026-41989 · CVE-2026-42198 · CVE-2026-42587 · CVE-2026-42779 · CVE-2026-43284 · CVE-2026-43500 · CVE-2026-4424 · CVE-2026-46863 · CVE-2026-47007 · CVE-2026-4800 · CVE-2026-54518 · CVE-2026-5588 · CVE-2026-5795 · CVE-2026-61053 · CVE-2026-61091 · CVE-2026-61095 · CVE-2026-61126 · CVE-2026-61127 · CVE-2026-61143 · CVE-2026-61223 · CVE-2026-61224 · CVE-2026-61225 · CVE-2026-61226 · CVE-2026-9256
RHSA-2026:9742: Red Hat Security Advisory: Red Hat Developer Hub 1.8.6 release.
CVE-2025-62718 · CVE-2025-69534 · CVE-2025-69873 · CVE-2026-1525 · CVE-2026-1526 · CVE-2026-1528 · CVE-2026-2229 · CVE-2026-3118 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-25679 · CVE-2026-26996 · CVE-2026-27601 · CVE-2026-27904 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-29186 · CVE-2026-32141 · CVE-2026-33036 · CVE-2026-33228 · CVE-2026-33891 · CVE-2026-33894 · CVE-2026-33895 · CVE-2026-33896 · CVE-2026-39983 · CVE-2026-40175
- Source published
- Mar 3, 2026, 10:38:38 PM (timezone not stated)
- Source modified
- Mar 4, 2026, 4:44:40 PM (timezone not stated)
- Saved here
- 15 Nov 2026 09:27:00 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 4.0 · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
nvd · CVE-2026-27601
PublishedUnderscore.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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-770
Original publisher date fields
published: 2026-03-03T23:15:55.560
lastModified: 2026-06-17T10:27:22.407
1 source CPE criteria · context only
- cpe:2.3:a:underscorejs:underscore:*:*:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 3 Mar 2026 23:15:55 UTC
- Source modified
- 17 Jun 2026 10:27:22 UTC
- Saved here
- 25 Oct 2026 06:17:33 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · [email protected] · Secondary · 8.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 · [email protected] · Primary · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-qpx9-hpmf-5gmw
Published### Impact In simple words, some programs that use `_.flatten` or `_.isEqual` could be made to crash. Someone who wants to do harm may be able to do this on purpose. This can only be done if the program has special properties. It only works in Underscore versions up to 1.13.7. A more detailed explanation follows. In affected versions of Underscore, 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. A proof of concept (PoC) for this type of attack with `_.isEqual`: ```js const _ = require('underscore'); // build JSON string for nested object ~4500 levels deep // (for this to be an attack, the JSON would have to come from // a request or other untrusted input) let json = ''; for (let i = 0; i < 4500; i++) json += '{"n":'; json += '"x"'; for (let i = 0; i < 4500; i++) json += '}'; // construct two distinct objects with equal shape from the above JSON const a = JSON.parse(json); const b = JSON.parse(json); _.isEqual(a, b); // RangeError: Maximum call stack size exceeded ``` A proof of concept (PoC) for this type of attack with `_.flatten`: ```js const _ = require('underscore'); // build nested array ~4500 levels deep // (like with _.isEqual, this nested array would have to be sourced // from an untrusted external source for it to be an attack) let nested = []; for (let i = 0; i < 4500; i++) nested = [nested]; _.flatten(nested); // RangeError: Maximum call stack size exceeded ``` An application that crashes because of this can be restarted, so the bug is most relevant to applications for which continued operation is important, such as server applications. Furthermore, an application is only vulnerable to this type of attack if ALL of the following conditions are met: - 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. All versions of Underscore up to and including 1.13.7 are affected by this weakness. ### Patches The problem has been patched in version 1.13.8. Upgrading to 1.13.8 or later completely prevents exploitation. **Note:** historically, there have been breaking changes in minor releases of Underscore, especially between versions 1.6 and 1.9. However, upgrading from version 1.9 or later to any later 1.x version should be feasible with little or no effort for all users. ### Workarounds A workaround that works for both functions is to enforce a depth limit on the datastructure that is created from untrusted input. A limit of 1000 levels should prevent attacks from being successful on most systems. In systems with highly constrained hardware, we recommend lower limits, for example 100 levels. Another possible workaround that only works for `_.flatten`, is to pass a second argument that limits the flattening depth to 1000 or less. ### References - https://github.com/jashkenas/underscore/issues/3011 - https://underscorejs.org/#1.13.8 - https://underscorejs.org/#flatten - https://underscorejs.org/#isEqual
- Source published
- 3 Mar 2026 17:46:06 UTC
- Source modified
- 10 Sep 2026 03:51:00 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Publisher rating · HIGH