Packagist
CVE-2026-55568
guzzlehttp/guzzle: Silent HTTPS-Proxy Downgrade to Cleartext
- Severity
- Medium 5.9
- Published
- 19 Jun 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 23 Oct 2026
- Fixed in
- 7.12.1
- Exploit chance
- 0.1% in the next 30 daysHigher than 4% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N- Also known as
- GHSA-wpwq-4j6v-78m3
- Sources
- OSV.dev and GitHub
Description
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 — a proxy reached over a TLS-encrypted connection — through the proxy request option, client-level proxy defaults, or proxy environment variables such as http_proxy, https_proxy, HTTPS_PROXY, all_proxy, and ALL_PROXY.
When the installed libcurl does not support HTTPS proxies, behavior depends on the libcurl version/build:
- 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.
- libcurl 7.50.2 through 7.51.x rejects the unsupported proxy scheme at connect time, so no cleartext exposure occurs, but the failure is late and opaque.
- libcurl 7.52.0 or newer builds without HTTPS-proxy support also fail at connect time rather than downgrading.
Workarounds
If you cannot upgrade immediately, do not configure an https:// proxy on an installation whose libcurl lacks HTTPS-proxy support, and verify the capability in application code before using one. Remember to check proxy environment variables as well as any explicit proxy option:
Upgrading the system libcurl to 7.52.0 or newer built with HTTPS-proxy support also resolves the underlying unsupported-proxy behavior.
Affected software
| Software | Affected versions |
|---|---|
guzzlehttp/guzzlePackagist · osv:Packagist:guzzlehttp/guzzle |
|
About guzzlehttp/guzzle
- Monthly downloads (Packagist)
- 35,230,404Packagist, 16 Nov 2026
- Total downloads (Packagist)
- 1,162,991,182Packagist, 16 Nov 2026
Vulnerabilities in guzzlehttp/guzzle
- In our list
- 9
- Published in the last 12 months
- 9
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-69246Guzzle: Noncanonical host can bypass host-based checksHigh 7.2 3 Aug 2026
- CVE-2026-69245Guzzle: Noncanonical cookie domain keeps subdomain scopeMedium 6.5 3 Aug 2026
- CVE-2026-67354Guzzle: URI fragments disclosed in redirect Referer headersMedium 5.9 20 Jul 2026
- CVE-2026-67355Guzzle: Host-only cookie scope is not preservedMedium 5.9 20 Jul 2026
- CVE-2026-67353Guzzle: Unbounded response cookies risk denial of serviceMedium 5.3 20 Jul 2026
- CVE-2026-59883Guzzle: Cookie Disclosure and Injection via IP-Address DomainsMedium 4.7 20 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-55568
- GitHub Advisory Database https://github.com/advisories/GHSA-wpwq-4j6v-78m3