This danger was utterly predictable, and heads need to roll at any place where it was put into a trusted production pipeline.

It kinds of reminds me of the Xerox JBIG2 bug which seamlessly corrupted scanned numbers [0], except that wasn't nearly as easy to see coming.

[0] http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...