The updated description shows that libcurl can erroneously reuse an authenticated connection for a different service when Negotiate authentication is employed, even when the services are distinct. This logical flaw in the connection-pooling criteria permits an attacker to use a pre-authenticated channel to access a service for which they lack authorization, leading to potential confidentiality or integrity compromise.

Any application that links against the libcurl library and uses Negotiate authentication with connection pooling is potentially impacted. The vendor is curl, product curl; no specific version information is disclosed in the CVE data, so all installations that employ these features should be considered at risk until a fix is applied.

The CVSS score of 6.5 indicates moderate severity, while the EPSS score of less than 1% and absence from the CISA KEV catalog suggest a low chance of exploitation. The updated description points to a logical error in libcurl's reuse logic. The likely attack vector is an application that can force libcurl to reuse a connection that was authenticated for one service to satisfy a request for another service on the same server. If an attacker can trigger this reuse, unauthorized access remains possible.