Development-test error via unchecked circular recursion
Published Jan 26, 2026 · Updated Jan 26, 2026
Uncontrolled recursion in ESLint before 9.26.0 allows local users to trigger a RuleTester error with a circular test-case object. During duplicate-test validation, checkDuplicateTestCase() passes the object to isSerializable(), which recursively traverses it without cycle detection. GitHub withdrew the advisory because RuleTester runs only during rule development and the condition raises an error rather than crashing an application.
Summary
What happened
Uncontrolled recursion in ESLint before 9.26.0 allows local users to trigger a RuleTester error with a circular test-case object. During duplicate-test validation, checkDuplicateTestCase() passes the object to isSerializable(), which recursively traverses it without cycle detection. GitHub withdrew the advisory because RuleTester runs only during rule development and the condition raises an error rather than crashing an application.
The record
- CVE
- CVE-2025-50537
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ESLint issue 19646 minimal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo