The issue arises from the native-to-JS bridging mechanism in the app, which requires a unique token to prevent non-app code from calling bridging functions. However, this token can potentially leak when used for downloading files, thus compromising the security of the bridging process.