Missing Check for Certificate Revocation after Initial Check

A single initial revocation check creates a dangerous race condition. If an attacker's certificate is revoked after that first check, the system will continue granting it full privileges for all later requests, as if the certificate were still valid. This essentially nullifies the security guarantee that revocation provides. Since certificate revocation almost always signals a compromise or malicious intent, failing to re-validate before each privileged action is a critical oversight. To prevent this, your code must perform a fresh revocation check (e.g., via OCSP or CRL) every time the certificate is used to authorize a sensitive operation, not just during the initial handshake or connection setup.