The issue arises when PDF.js is used to load a malicious PDF, and PDF.js is configured with `isEvalSupported` set to `true`, which is the default value. This configuration allows unrestricted attacker-controlled JavaScript to be executed in the context of the hosting domain.