This is pretty much exactly the kind of problem that one might expect with WebGL. Since driver writers traditionally didn't think much about security implications, this may be a simple case of somebody "forgetting" (possibly motivated by performance considerations) to zero out texture contents. The people responsible for that code should fix it and then we can all move on.