Stack overflow vulnerability in eslint before 9.26.0 when serializing objects with circular references in eslint/lib/shared/serialization.js. The exploit is triggered via the RuleTester.run() method, which validates test cases and checks for duplicates. During validation, the internal function checkDuplicateTestCase() is called, which in turn uses the isSerializable() function for serialization checks. When a circular reference object is passed in, isSerializable() enters infinite recursion, ultimately causing a stack overflow.
Metrics
Affected Vendors & Products
References
History
Wed, 28 Jan 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | eslint: eslint: Denial of Service via stack overflow when serializing objects with circular references | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 27 Jan 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eslint
Eslint eslint |
|
| Vendors & Products |
Eslint
Eslint eslint |
Mon, 26 Jan 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 26 Jan 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-674 | |
| Metrics |
cvssV3_1
|
Mon, 26 Jan 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Stack overflow vulnerability in eslint before 9.26.0 when serializing objects with circular references in eslint/lib/shared/serialization.js. The exploit is triggered via the RuleTester.run() method, which validates test cases and checks for duplicates. During validation, the internal function checkDuplicateTestCase() is called, which in turn uses the isSerializable() function for serialization checks. When a circular reference object is passed in, isSerializable() enters infinite recursion, ultimately causing a stack overflow. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-01-26T16:16:34.731Z
Reserved: 2025-06-16T00:00:00.000Z
Link: CVE-2025-50537
Updated: 2026-01-26T16:15:56.018Z
Status : Awaiting Analysis
Published: 2026-01-26T16:15:58.330
Modified: 2026-01-27T14:59:34.073
Link: CVE-2025-50537