Bug 2491767 (CVE-2026-55568) - CVE-2026-55568 guzzlehttp/guzzle: Guzzle: Information disclosure via cleartext proxy communication
Summary: CVE-2026-55568 guzzlehttp/guzzle: Guzzle: Information disclosure via cleartex...
Keywords:
Status: NEW
Alias: CVE-2026-55568
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2491788 2491789 2491791 2491793
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-23 16:01 UTC by OSIDB Bzimport
Modified: 2026-06-23 16:17 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-23 16:01:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.