This is as much the security researcher's fault as it is Apple's. Normally researchers follow "responsible disclosure", where they tell the company about a security vulnerability and then work with the company as the company fixes it. This means that the company has a chance to fix the problem before it's publicly known.<br><br>That does <i>not</i> seem to have happened here. At least, there's no evidence that it did. The page TechLinked showed, at least when I read it yesterday, contained no information about the disclosure timeline - e.g. when it was reported to Apple, when Apple said they had a fix, etc. In the normal process this mistake would have been noticed by the researcher. This reeks of Apple being forced to rush a fix because the researcher irresponsibly published early.<br><br>To provide more context I wish TechLinked had provided, vulnerabilities like this are not uncommon. This is a particularly bad one (relatively easy to exploit + high severity RCE), but virtually every project has security vulnerabilities, so don't read this as Apple being more insecure: Microsoft and Google have security bugs too. (It's also hard to quantify software security by looking at vulnerability count in a vacuum: if A issues more security patches than B, does that mean A has more security bugs or does it mean that A is simply more popular and therefore getting more attention?),(reply>), To be clear, I am NOT asserting that Android, Windows, macOS and iOS are all equally (in)secure. What I AM asserting is that interpreting this bug, which <i>happens to</i> have gotten a lot of press, in a vacuum is likely to lead you to very incorrect conclusions.