Comment 25 for bug 909569

This issue is not exploitable by itself. However, it is considered a security issue as it could potentially result in an increase in what could be accomplished by exploiting another security vulnerability in Swift.

Seems a little clumsy to me, perhaps:
We do not believe that this vulnerability is directly exploitable but it may be possible to leverage it as part of an attack involving other vulnerabilities in Swift....