diff --git a/build.js b/build.js index ce76f7ec61ace..570559f14d7bc 100755 --- a/build.js +++ b/build.js @@ -272,9 +272,9 @@ function getSource (callback) { lts: latestVersion.lts(versions) }, banner: { - visible: false, - text: 'Security releases may be necessary for all release lines', - link: '/en/blog/vulnerability/april-2020-openssl-updates/' + visible: true, + text: 'New security releases to be made available June 2, 2020', + link: '/en/blog/vulnerability/june-2020-security-releases/' } } } diff --git a/locale/en/blog/vulnerability/june-2020-security-releases.md b/locale/en/blog/vulnerability/june-2020-security-releases.md new file mode 100644 index 0000000000000..2c2555cf3f299 --- /dev/null +++ b/locale/en/blog/vulnerability/june-2020-security-releases.md @@ -0,0 +1,28 @@ +--- +date: 2020-05-26T12:00:00.000Z +category: vulnerability +title: June 2020 Security Releases +slug: june-2020-security-releases +layout: blog-post.hbs +author: Sam Roberts +--- + +## Summary + +The Node.js project will release security updates to all supported release lines on or shortly after Tuesday, June 2nd, 2020. + +The highest severity fix will be "High". + +## Impact + +All supported versions (10.x, 12.x, and 14.x) of Node.js are vulnerable. Note that 13.x will be end-of-life on June 1st, before the security release date, and according to policy it will ***not*** receive any more updates. + +## Release timing + +Releases will be available on or shortly after Tuesday, June 2nd, 2020. + +## Contact and future updates + +The current Node.js security policy can be found at https://nodejs.org/en/security/. Please follow the process outlined in https://github.com/nodejs/node/blob/master/SECURITY.md if you wish to report a vulnerability in Node.js. + +Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the nodejs GitHub organization.