Using the ThreadPool.UnsafeQueueNativeOverlapped(NativeOverlapped*) method could inadvertently open up a security hole. Code access security bases its permission checks on the permissions of all the callers on the stack. When work is queued on a thread pool thread using ThreadPool.UnsafeQueueNativeOverlapped(NativeOverlapped*), the stack of the thread pool thread does not have the context of the actual callers. Malicious code might be able exploit this to avoid permission checks.