guzzlehttp/guzzle vulnerabilities
Guzzle is a PHP HTTP client library
- Registry
- Composer
- Latest
- 8.3.0
- License
- MIT
15 known advisories
The latest version, 8.3.0, is not affected by any of them. Projects on older versions may be.
composer require guzzlehttp/guzzle:^8.3.0Security advisories for guzzlehttp/guzzle
Guzzle: Noncanonical host can bypass host-based checks
- Affected
- <7.15.2 · >=8.0.0 <8.0.1
- Fixed in
- 7.15.2, 8.0.1
Guzzle: Noncanonical cookie domain keeps subdomain scope
- Affected
- <7.15.2 · >=8.0.0 <8.0.1
- Fixed in
- 7.15.2, 8.0.1
Guzzle: URI fragments disclosed in redirect Referer headers
- Affected
- <7.15.1
- Fixed in
- 7.15.1
Guzzle: Host-only cookie scope is not preserved
- Affected
- <7.15.1
- Fixed in
- 7.15.1
Guzzle: Unbounded response cookies risk denial of service
- Affected
- <7.15.1
- Fixed in
- 7.15.1
Guzzle: Cookie Disclosure and Injection via IP-Address Domains
- Affected
- <7.12.3
- Fixed in
- 7.12.3
Guzzle: Proxy-Authorization headers can be sent to origin servers
- Affected
- <7.14.2
- Fixed in
- 7.14.2
guzzlehttp/guzzle: Dot-Only Cookie Domains Match All Hosts
- Affected
- <7.12.1
- Fixed in
- 7.12.1
guzzlehttp/guzzle: Silent HTTPS-Proxy Downgrade to Cleartext
- Affected
- <7.12.1
- Fixed in
- 7.12.1
Change in port should be considered a change in origin
- Affected
- <6.5.8 · >=7.0.0 <7.4.5
- Fixed in
- 6.5.8, 7.4.5
CURLOPT_HTTPAUTH option not cleared on change of origin
- Affected
- <6.5.8 · >=7.0.0 <7.4.5
- Fixed in
- 6.5.8, 7.4.5
Failure to strip the Cookie header on change in host or HTTP downgrade
- Affected
- >=4.0.0 <6.5.7 · >=7.0.0 <7.4.4
- Fixed in
- 6.5.7, 7.4.4
Fix failure to strip Authorization header on HTTP downgrade
- Affected
- >=4.0.0 <6.5.7 · >=7.0.0 <7.4.4
- Fixed in
- 6.5.7, 7.4.4
Cross-domain cookie leakage in Guzzle
- Affected
- <6.5.6 · >=7.0.0 <7.4.3
- Fixed in
- 6.5.6, 7.4.3
HTTP Proxy header vulnerability
- Affected
- >=6 <6.2.1 · >=4.0.0-rc2 <4.2.4 · >=5 <5.3.1
- Fixed in
- 4.2.4, 5.3.1, 6.2.1
Which of your client projects still run an old guzzlehttp/guzzle?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.