libcurl maintains a connection pool to reuse connections for subsequent transfers if they match the setup. However, when an easy handle first uses the default native CA trust store and later switches to custom CA material, it may continue trusting the native platform's CA store due to connection reuse. This can cause the handle to accept certificates trusted by the native store despite the application's intent to use a different trust configuration.

The vulnerability may cause libcurl to trust certificates from the native platform CA store even when the application has switched to custom CA certificates. This could lead to unintended trust of TLS connections, potentially undermining the application's security policy regarding certificate validation.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid reusing easy handles across transfers with different CA trust configurations or explicitly close and recreate handles when changing CA material.