Processing a certificate containing numerous `nameRelativeToCRLIssuer` CRL distribution points can cause disproportionate heap growth when X.509 extensions are cached. A malicious peer can send a crafted certificate that, while remaining under the accepted size limit of approximately 100 KiB, triggers the allocation of several hundred MiB of resident memory during a standard TLS handshake. This excessive memory allocation can lead to significant memory pressure and a potential Denial of Service, potentially crashing the client or server if multiple concurrent connections occur.