Interestingly this was not part of the original iOS11 security announcement: http://web.archive.org/web/20170919182359/https://support.apple.com/en-us/HT208112

Interestingly this was not part of the original iOS11 security announcement: http://web.archive.org/web/20170919182359/https://support.apple.com/en-us/HT208112 http://web.archive.org/web/20170919182359/https://support.ap... and (a mail to apple-security which is no longer archived at https://lists.apple.com/archives/security-announce/2017/Sep/threads.html#00000 https://lists.apple.com/archives/security-announce/2017/Sep/... ) But instead published after the fact as an additional update: https://lists.apple.com/archives/security-announce/2017/Sep/msg00002.html https://lists.apple.com/archives/security-announce/2017/Sep/... and https://support.apple.com/en-us/HT208112 https://support.apple.com/en-us/HT208112 Why delay the announcement? And why remove the original "APPLE-SA-2017-09-19-1 iOS 11" with "Date: Tue, 19 Sep 2017 -0700" from the apple-security email archive? Also, are Macbooks vulnerable to the same bug until next monday when macOS 10.13 drops? Also, there are about 6 other similar issues recently posted to Google Project Zero: https://bugs.chromium.org/p/project-zero/issues/list?can=1&q=owner:laginimaineb@google.com&sort=-id https://bugs.chromium.org/p/project-zero/issues/list?can=1&q...