-
-
Notifications
You must be signed in to change notification settings - Fork 128
CVE to EOL lines: Tracking Issue #1419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Any reason to start at 14? Can we do 17 and all earlier versions as one CVE? |
Sure, I thought about issuing CVE for v14 <= and then a new one of each one of the release lines listed but starting on v17 makes sense. I'll update the description. |
This issue has been inactive for 90 days. It will be closed in 14 days unless there is further activity or the stale label is taken off. |
Closing it as CVE to EOL lines is not a thing anymore. Instead, we are following #1445 approach. |
Until we find a better place to have it listed, let's use this issue to track the CVE issues for EOL versions of Node.js.
v19.x
v21.x
cc: @nodejs/security-release
The text was updated successfully, but these errors were encountered: