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.
CVE-2026-27601
This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 60%
- KEV
- Not listed
Published
March 3, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 4, 2026Unlimited recursion in _.flatten and _.isEqual, potential for DoS attack · Advisory · jashkenas/underscore · GitHub
Affected: version 1.13.8. Upgrading to 1.13.8 or later completely prevents exploitation.
https://github.com/jashkenas/underscore/security/advisories/GHSA-qpx9-hpmf-5gmwcommit a6e23ae96474 (jashkenas/underscore)
Fix landed in jashkenas/underscore commit a6e23ae96474 — awaiting tagged release
https://github.com/jashkenas/underscore/commit/a6e23ae9647461ec33ad9f92a2ecfc220eea0a84commit 411e222eb0ca (jashkenas/underscore)
Fix landed in jashkenas/underscore commit 411e222eb0ca — awaiting tagged release
https://github.com/jashkenas/underscore/commit/411e222eb0ca5d570cc4f6315c02c05b830ed2b4Vendor Advisories for CVE-2026-27601(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:24841Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Developer Hub 1.10.0 release.
- CVE-2026-27601Microsoft Security Response Center (MSRC)High
Underscore.js has unlimited recursion in _.flatten and _.isEqual, potential for DoS attack
- RHSA-2026:13826Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Developer Hub 1.9.4 release.
- RHSA-2026:9742Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Developer Hub 1.8.6 release.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhdh/rhdh-hub-rhel9:1780930740 | 2026-06-09 | redhat |
| redhat | rhdh/rhdh-hub-rhel9:1777903262 | 2026-05-05 | redhat |
| redhat | rhdh/rhdh-hub-rhel9:1776784286 | 2026-04-22 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| underscore | 1.13.2~dfsg-1 ... 1.9.1~dfsg-4 (15 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| underscore | 1.13.4~dfsg+~1.11.4-3 ... 1.13.8~dfsg+~1.13.0-1 (8 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| underscore | 1.13.4~dfsg+~1.11.4-3 ... 1.13.8~dfsg+~1.13.0-1 (8 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| underscore | 1.13.4~dfsg+~1.11.4-3 ... 1.13.7~dfsg+~1.13.0-6 (7 versions) | 1.13.8~dfsg+~1.13.0-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| underscore | — | 1.13.8 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 28× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 196 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 18:50 UTCOSV refresh
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 22:04 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:38 UTCEG score recompute
- 2026-08-14 08:38 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 00:28 UTCEG score recompute
- 2026-08-13 00:28 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 07:56 UTCEG score recompute
- 2026-08-11 07:56 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:09 UTCEG score recompute
- 2026-08-10 08:09 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:16 UTCEG score recompute
- 2026-08-09 08:16 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:10 UTCEG score recompute
- 2026-08-07 20:10 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:44 UTCEG score recompute
- 2026-08-06 02:44 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 04:28 UTCEG score recompute
- 2026-08-04 04:28 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:03 UTCEG score recompute
- 2026-08-02 19:03 UTCVendor advisory
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:08 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 10:29 UTCOSV refresh
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-27601?
When was CVE-2026-27601 disclosed?
Is CVE-2026-27601 actively exploited?
What is the CVSS score of CVE-2026-27601?
How do I remediate CVE-2026-27601?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27601
Is Your Infrastructure Affected by CVE-2026-27601?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.