Количество 13
Количество 13
GHSA-8whr-249c-vfjp
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
CVE-2026-3783
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
CVE-2026-3783
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
CVE-2026-3783
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
CVE-2026-3783
token leak with redirect and netrc
CVE-2026-3783
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that ...
BDU:2026-04361
Уязвимость программного средства для взаимодействия с серверами cURL, связанная с недостаточной защитой регистрационных данных, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
ROS-20260410-73-0014
Уязвимость curl
SUSE-SU-2026:0921-1
Security update for curl
openSUSE-SU-2026:20404-1
Security update for curl
SUSE-SU-2026:0911-1
Security update for curl
SUSE-SU-2026:0903-1
Security update for curl
SUSE-SU-2026:0885-1
Security update for curl
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-8whr-249c-vfjp When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one. | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
CVE-2026-3783 When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one. | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
CVE-2026-3783 When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one. | CVSS3: 5.7 | 0% Низкий | 5 месяцев назад | |
CVE-2026-3783 When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one. | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
CVE-2026-3783 token leak with redirect and netrc | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
CVE-2026-3783 When an OAuth2 bearer token is used for an HTTP(S) transfer, and that ... | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
BDU:2026-04361 Уязвимость программного средства для взаимодействия с серверами cURL, связанная с недостаточной защитой регистрационных данных, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации | CVSS3: 5.3 | 0% Низкий | 5 месяцев назад | |
ROS-20260410-73-0014 Уязвимость curl | CVSS3: 5.3 | 0% Низкий | 4 месяца назад | |
SUSE-SU-2026:0921-1 Security update for curl | 5 месяцев назад | |||
openSUSE-SU-2026:20404-1 Security update for curl | 5 месяцев назад | |||
SUSE-SU-2026:0911-1 Security update for curl | 5 месяцев назад | |||
SUSE-SU-2026:0903-1 Security update for curl | 5 месяцев назад | |||
SUSE-SU-2026:0885-1 Security update for curl | 5 месяцев назад |
Уязвимостей на страницу