You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,6 @@ CVEs for the base operating system image packages should be reported to those re
13
13
14
14
When base images are patched, the images are rebuilt and rolled out to the Docker hub without intervention by this repo. This process is explained in <https://github.com/docker-library/faq/#why-does-my-security-scanner-show-that-an-image-has-cves>.
15
15
16
-
When vulnerabilities are resolved in a Node.js release, they are routinely released in a corresponding new Node.js Docker image from time to time as needed.
16
+
When vulnerabilities are resolved in a Node.js release, they are routinely released in a corresponding new Node.js Docker image. The schedule is determined by the Node.js releases not by the Node.js Docker repo.
17
17
18
18
Please do not open issues in this repo for vulnerabilities in the above components. If they cannot be actioned here, the issue will be closed.
0 commit comments