Impact The attacker, with one captured signed SOAP envelope from a victim and no other privileges, can invoke arbitrary operations on the service as the victim principal for the lifetime of the captured signing key. There is no rate limit on replays. The DetectReplays setting on transport-security bindings does not mitigate the issue because the attack does not reuse the original timestamp — the fresh timestamp in the wsse:Security header is what the replay-detection logic inspects. Patches Fixed in CoreWCF v1.8.1 and v1.9.1 Workarounds Ensure communication is protected by SSL/TLS to prevent capturing of signed SOAP envelope.