If only Google had the ability to custom compile FFmpeg to only include robust mainstream codecs.
In such a would they might even handball submitted obscure codecs to a full build in a sandbox to track bleeding edge malware.
Right, they probably already mitigated this bug in their own usage. Which is exactly why reporting the bug is a FAVOR to ffmpeg. Would you rather they just quietly fix it on their own and not report it to the maintainers?
To my understanding this bug would affect anyone using ffmpeg on untrusted input. Google may already be limiting to certain codecs in their own use, but should still report the issue (as they have here).