https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T06:40:09.024230+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2022-03953 bdu:2022-03953 2026-10-04T06:40:09.124069+00:00 bdu:2022-03953 https://cve.radiocsirt.org/vuln/bit-drupal-2022-31042 BIT-drupal-2022-31042 — Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle 2026-10-04T06:40:09.124111+00:00

Affected: Bitnami: drupal

Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

 https://cve.radiocsirt.org/vuln/certfr-2022-avi-541 certfr-2022-avi-541 — De multiples vulnérabilités ont été découvertes dans Drupal Core. Elles permettent à un attaquant de provoquer une atte… 2026-10-04T06:40:09.124152+00:00 certfr-2022-avi-541 https://cve.radiocsirt.org/vuln/euvd-2026-234066 EUVD-2026-234066 2026-10-04T06:40:09.124171+00:00 EUVD-2026-234066 https://cve.radiocsirt.org/vuln/fkie_cve-2022-31042 fkie_cve-2022-31042 2026-10-04T06:40:09.124183+00:00

Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

 https://cve.radiocsirt.org/vuln/ghsa-f2wf-25xc-69c9 GHSA-f2wf-25xc-69c9 — Failure to strip the Cookie header on change in host or HTTP downgrade 2026-10-04T06:40:09.124211+00:00

Affected: Packagist: guzzlehttp/guzzle

### Impact

`Cookie` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there.

### Patches

Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.

### Workarounds

An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

### References

* [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx)

### For more information

If you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the [PHP HTTP Slack](https://php-http.slack.com/). Do not report additional security advisories in that public channel, however - please follow our [vulnerability reporting process](https://github.com/guzzle/g…

 https://cve.radiocsirt.org/vuln/gsd-2022-31042 gsd-2022-31042 2026-10-04T06:40:09.124255+00:00 gsd-2022-31042 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31042 UBUNTU-CVE-2022-31042 2026-10-04T06:40:09.124267+00:00

Affected: Ubuntu:24.04:LTS: guzzle, Ubuntu:25.10: guzzle, Ubuntu:26.04:LTS: guzzle

Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.