One of the nice things about WordPress is that it automatically updates itself with critical security updates, so issues like this get taken care of automatically.
That said, I just manually updated to 4.2.1 when I went to write a post on my site. So it's nice to know I'm safe from this particular exploit either way. :-D