Now, since I did have MapsGL enabled, it says it's been integrated into the new Google Maps that's being previewed here.
Currently, the biggest security risk in WebGL is, indirectly, your graphics driver. As an example, the latest security problem with WebGL was in OS X and had to to with exposing uninitialized memory contents. Of course, it is true that graphics driver writers are only now warming up to the fact that a webpage shouldn't cause a kernel panic and that it shouldn't leak uninitialized memory. Still, the WebGL spec itself has fixed all of the early problems it had.
Sorry if you were aware of this distinction! I hear many people talking about WebGL security issues as they existed in the draft, and I think some clarification of the public opinion is in order.
(And, to be perfectly nitpicky, in Windows you'd be blaming Direct3D drivers ;) ANGLE compiles WebGL to Direct3D.)
Not caring about attacks from the local user is what got Microsoft tons of (justified) bad PR not ten years ago.
It is not ready for prime time and I shudder to think what people on older machines or laptops are going to experience.