Approved changes feed: RSS · Atom
cpe:2.3:a:guzzle:guzzle:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Guzzle (df9889de-8927-5c7c-a1b8-b3b34b9554f5) |
|---|---|
| Product | Guzzle (52679864-13cd-5ede-9dd2-7170ec440330) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-69245 |
vulnerable | 2026-09-16 04:34:19.699304 |
Guzzle: Noncanonical cookie domain keeps subdomain scope
MEDIUM (6.5)
Guzzle is an extensible PHP HTTP client. Prior to 7.15.2 and 8.0.1, SetCookie::matchesDomain() gives every subdomain of a cookie Domain that cookie unless SetCookie::matchesDomain() recognizes the Domain as an IP literal or a numeric host, and the decision comes from the domain's own text, so two spellings a transport reads as an address keep subdomain scope. Hexadecimal and mixed-base forms such as 0x7f000001 and 0177.0.0.0x1 go unrecognized while libcurl 8.21.0 reads both as 127.0.0.1. A percent-escaped Domain keeps that scope on both branches because percent-decoding sits above numeric parsing, so 192.168.0.%31 and 127.0.0.1%2e are registered names in the URI grammar rather than address literals, and no numeric rule in any base classifies them, while libcurl decodes the host before resolving and reads them as 192.168.0.1 and 127.0.0.1. A cookie stored for Domain=0x7f000001 is placed in the Cookie header of a request to evil.0x7f000001, disclosing a session identifier or token to a host that is not that address, and a response from evil.0x7f000001 setting Domain=0x7f000001 is accepted into the jar and replayed to the address, so a server answering for the look-alike name can fix a session or set application state. Exploitation requires the application to enable cookie support, address an origin by one of these spellings, and contact a host whose name ends in that spelling. This issue is fixed in versions 7.15.2 and 8.0.1.
Published: 2026-08-03T21:05:08.259Z
Updated: 2026-08-04T15:04:58.047Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-69246 |
vulnerable | 2026-09-16 04:34:17.709107 |
Guzzle: Noncanonical host can bypass host-based checks
HIGH (7.2)
Guzzle is an extensible PHP HTTP client. Prior to 7.15.2 and 8.0.1, Guzzle gives a transport the request URI as text and supplies the Host header separately. The cURL handlers set CURLOPT_URL to the URI exactly as written and push that Host into CURLOPT_HTTPHEADER; StreamHandler does the same through fopen(). libcurl then parses the authority itself, percent-decoding it and, on an IDN-capable build, applying IDNA mapping, and uses the result to resolve, connect, name the TLS peer and address a proxy CONNECT, while the supplied Host suppresses the aligned one libcurl would have generated. For a URI host written as 127.0.0.%31, filter_var() rejects the host as an IP literal, yet libcurl decodes it to 127.0.0.1 and reaches loopback with no DNS lookup while the server receives Host: 127.0.0.%31. An attacker who influences a fetched URI can therefore reach a host the application's checks excluded and read whatever the host exposes of the response. The same divergence moves Guzzle's own decisions onto a spelling the transport does not use: no_proxy selects proxy routing from the literal host, and RedirectMiddleware decides from it whether to strip Authorization and Cookie. Exploitation requires the application to build a request URI from untrusted input and to make a host decision before handing it to Guzzle. This issue is fixed in versions 7.15.2 and 8.0.1.
Published: 2026-08-03T21:07:04.228Z
Updated: 2026-08-04T14:06:40.238Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-67339 |
vulnerable | 2026-09-16 04:33:05.962516 |
guzzlehttp/guzzle before 7.14.2 Proxy-Authorization Header Disclosure
MEDIUM (5.3)
guzzlehttp/guzzle versions before 7.14.2 fail to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.
Published: 2026-08-01T12:22:17.139Z
Updated: 2026-10-08T15:24:13.572Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-67353 |
vulnerable | 2026-09-16 04:33:05.928742 |
guzzlehttp/guzzle before 7.15.1 Unbounded Cookie Denial of Service
MEDIUM (5.3)
guzzlehttp/guzzle versions before 7.15.1 contain a denial of service vulnerability in the CookieJar that accepts unlimited Set-Cookie header fields with no size restrictions. Attackers can return many large cookies from a malicious server, causing Guzzle to store excessive data in memory and generate oversized Cookie headers that fail in handlers or destination servers.
Published: 2026-08-01T12:22:17.339Z
Updated: 2026-10-08T15:24:15.436Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-67355 |
vulnerable | 2026-09-16 04:33:05.819687 |
guzzlehttp/guzzle before 7.15.1 Host-only Cookie Scope
MEDIUM (5.9)
guzzlehttp/guzzle versions before 7.15.1 fail to preserve host-only cookie scope, storing the request host in the Domain field instead of marking cookies as host-only. Attackers controlling child hosts can receive host-only cookies intended only for parent hosts, potentially disclosing session identifiers and authorization tokens when the same cookie jar is reused across trust boundaries.
Published: 2026-08-01T12:22:17.646Z
Updated: 2026-10-08T15:24:16.706Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-67354 |
vulnerable | 2026-09-16 04:33:05.723627 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-59883 |
vulnerable | 2026-07-29 01:03:18.036003 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55767 |
vulnerable | 2026-07-29 01:00:28.623568 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55568 |
vulnerable | 2026-07-29 01:00:28.502355 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31091 |
vulnerable | 2026-06-08 05:43:40.135857 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31090 |
vulnerable | 2026-06-08 05:43:40.135249 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31043 |
vulnerable | 2026-06-08 05:43:40.048836 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31042 |
vulnerable | 2026-06-08 05:43:40.044638 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29248 |
vulnerable | 2026-06-08 05:42:47.427658 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.