Thanks for the reply.
So in other words, the error was *not* fixed/included in the most recent release (v.2.2.4 or 2.2.5)?
I don't have Jetpack on my site. My concern was the vast amount of WP sites I see with this error. I was concerned it might be a new vulnerability, rather than just a coding error, since it's surprising it's so pervasive.