[GHSA-p5wg-g6qr-c7cg] eslint has a Stack Overflow when serializing objects with circular references

[lukemcgregor]

Updates

• CWEs
• Summary

Comments
A possible stack overflow in eslint shouldn't be a security vulnerability. Eslint is running on trusted or semi trusted input, if it fails in this manor its not going to cause service outages, data leakages or remote access. By allowing 'security issues' like this into the database you are undermining trust in the database as a whole.

This should be getting reoported on eslint issues on their repo, not in the vulnerability db

[Copilot]

Pull request overview

This PR modifies a GitHub Security Advisory (GHSA) to reclassify an ESLint stack overflow issue as not being a security vulnerability. The change reflects the position that stack overflow issues in developer tools like ESLint, which run on trusted input, should not be treated as security vulnerabilities.

Changes:

• Updated the advisory summary from describing a specific vulnerability to "Not a vulnerability"
• Removed the CWE-674 classification (Uncontrolled Recursion)
• Updated the modification timestamp

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[advisory-database]

Hi @lukemcgregor! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!