IBM Planning Analytics Local 2.1.0 through 2.1.17 could allow an attacker to trick the caching mechanism into storing and serving sensitive, user-specific responses as publicly cacheable resources.
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.