As I understand the fix is to update the JCS instances, you can check the version by logging into your Java Console and in the "General" section you have the version number. If the version is 13.2 then the issue exists, once it is updated to 14.1 it will be fixed. I confirmed that the issue does not exist in 14.1. AFAIK the update should happen in next few days across all instances.
Fusion Applications Developer Relations