CVEvulnerability

CVE-2026-55568

5.9 MEDIUM Published 2026-06-23 Modified 2026-06-26 Official page ↗
Status
Analyzed
Published
2026-06-23
Last modified
2026-06-26
Assigner
[email protected]
CVSS 3.1 ([email protected])
5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-311, CWE-319, CWE-636

Description

Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization header, proxy userinfo in the proxy URL, or CURLOPT_PROXYUSERPWD) are sent without encryption, and the CONNECT target host and port for tunneled HTTPS requests are exposed. The built-in cURL handlers (GuzzleHttp\Handler\CurlHandler and GuzzleHttp\Handler\CurlMultiHandler, used by default whenever the PHP cURL extension is available) accept an https:// proxy. libcurl older than 7.50.2 silently treats an https:// proxy as a plaintext http:// proxy. The TLS connection to the proxy is never established, and the proxy leg is cleartext with no error or warning. An application is affected when it sends requests through one of the built-in cURL handlers, configures an https:// proxy expecting the proxy connection itself to be encrypted, and runs with libcurl older than 7.50.2. This vulnerability is fixed in 7.12.1.

Affected configurations

• guzzlephp guzzle (< 7.12.1)

Related

Weakness · CWE (3)

  • CWE-311 Missing Encryption of Sensitive Data weakness
  • CWE-319 Cleartext Transmission of Sensitive Information weakness
  • CWE-636 Not Failing Securely weakness

References