REDHAT-BUG-2496764: High severity curl libcurl vulnerability
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different 'services'.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
Affected Software
Event History
Frequently Asked Questions
Which application flows are exposed to the incorrect connection reuse?
The affected flow involves libcurl requests using Negotiate authentication for different services on the same server. Exposure requires an existing pooled connection authenticated for one service to be reused for a request intended for another service.
What needs to be present for the issue to occur?
Libcurl must have a recent connection available in its connection pool, and the application must issue a Negotiate-authenticated request to the same server using a different service. The logical error affects the criteria used when deciding whether that existing connection can be reused.
Which Red Hat advisories are listed for this issue?
The listed advisories are RHSA-2026:69125, RHSA-2026:69126, and RHSA-2026:72506. The provided data does not identify the affected or fixed package versions.