Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to detect that the server was not authenticated. This occurs because TLS and DTLS handshakes do not abort as expected when the `SSL VERIFY PEER` verification mode is set. This issue can lead to man-in-the-middle attacks if the client relies on the handshake failure to identify an authentication mismatch. RPKs are disabled by default; the issue only manifests when clients explicitly enable RPK use and the server sends an RPK instead of an X.509 certificate chain. Clients that verify the result by calling the `SSL get verify result()` function and take appropriate action are not affected. FIPS modules in versions 3.0 through 3.4 are not impacted.