Yup, we discovered this on the 11th. We are tracking the issue here, and there's already a discussion over here. The issue thread includes some workaround for now as well.
We have a fix coming in a release that should be released soon in the 4.1.x and 4.5.x version. We're also looking at possibly backporting the fix into 4.x versions, but that's still being discussed.