Поиск уязвимостей
Количество 18
Количество 18
GHSA-6g7g-56fm-f8mp
libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials wh...
CVE-2026-5545
libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when ...
CVE-2026-5545
libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when ...
CVE-2026-5545
libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when
CVE-2026-5545
wrong reuse of HTTP Negotiate connection
CVE-2026-5545
libcurl might in some circumstances reuse the wrong connection when as ...
ROS-20260624-80-0039
Уязвимость curl
BDU:2026-09771
Уязвимость программного средства для взаимодействия с серверами cURL, связанная с неверным сроком действия сеанса, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
ROS-20260624-73-0039
Уязвимость curl
openSUSE-SU-2026:20973-1
Security update for curl
RLSA-2026:80512
Moderate: curl security update
ELSA-2026-80512
ELSA-2026-80512: curl security update (MODERATE)
SUSE-SU-2026:2703-1
Security update for curl
SUSE-SU-2026:1940-1
Security update for curl
SUSE-SU-2026:1717-1
Security update for curl
SUSE-SU-2026:3798-1
Security update for curl
ALT-PU-2026-6924
ALT-PU-2026-6924: package `curl` update to version 8.20.0-alt1
ALT-PU-2026-18300
ALT-PU-2026-18300: package `libcurl4-openssl` update to version 8.22.0-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-6g7g-56fm-f8mp libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials wh... | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
CVE-2026-5545 libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when ... | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
CVE-2026-5545 libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when ... | CVSS3: 6.5 | 0% Низкий | 7 месяцев назад | |
CVE-2026-5545 libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. 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 credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
CVE-2026-5545 wrong reuse of HTTP Negotiate connection | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
CVE-2026-5545 libcurl might in some circumstances reuse the wrong connection when as ... | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
ROS-20260624-80-0039 Уязвимость curl | CVSS3: 6.5 | 0% Низкий | 5 месяцев назад | |
BDU:2026-09771 Уязвимость программного средства для взаимодействия с серверами cURL, связанная с неверным сроком действия сеанса, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации | CVSS3: 6.5 | 0% Низкий | 6 месяцев назад | |
ROS-20260624-73-0039 Уязвимость curl | CVSS3: 6.5 | 0% Низкий | 5 месяцев назад | |
openSUSE-SU-2026:20973-1 Security update for curl | 5 месяцев назад | |||
RLSA-2026:80512 Moderate: curl security update | около 1 месяца назад | |||
ELSA-2026-80512 ELSA-2026-80512: curl security update (MODERATE) | около 1 месяца назад | |||
SUSE-SU-2026:2703-1 Security update for curl | 5 месяцев назад | |||
SUSE-SU-2026:1940-1 Security update for curl | 6 месяцев назад | |||
SUSE-SU-2026:1717-1 Security update for curl | 7 месяцев назад | |||
SUSE-SU-2026:3798-1 Security update for curl | 3 месяца назад | |||
ALT-PU-2026-6924 ALT-PU-2026-6924: package `curl` update to version 8.20.0-alt1 | CVSS3: 7.5 | 7 месяцев назад | ||
ALT-PU-2026-18300 ALT-PU-2026-18300: package `libcurl4-openssl` update to version 8.22.0-alt1 | CVSS3: 9.8 | около 1 месяца назад |
Уязвимостей на страницу