It looks like this issue was found and fixed back in late March so any of the recent hotfixes should include the fix for this.