High

Change in port should be considered a change in origin

  • Disclosed: 21.06.2022
  • Updated: 11.10.2026 10:22

Impact

Authorization and Cookie headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the Authorization and Cookie headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. Now, we consider any change in host, port or scheme to be a change in origin.

Patches

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

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

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. Do not report additional security advisories in that public channel, however please follow our vulnerability reporting process.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package guzzlehttp/guzzle < 6.5.8, >= 7.0.0, < 7.4.5 6.5.8, 7.4.5

References

CVSS score 7.7/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness (CWE)
CWE-200
Platform
Composer
Package
guzzlehttp/guzzle
Disclosed
21.06.2022
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-q559-8m2m-g699 - CC BY 4.0

Vulnerability history: guzzlehttp/guzzle

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (14) in the archive
Total entries
14
First → latest
04.2022 08.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 6
  • Medium 8

Disclosures per year

  1. 2022: 5
  2. 2023: 0
  3. 2024: 0
  4. 2025: 0
  5. 2026: 9
Severity:
  1. High · 7.2 CVE-2026-69246 < 7.15.2, >= 8.0.0, < 8.0.1 7.15.2, 8.0.1
  2. Change in port should be considered a change in origin this entry
    High · 7.7 CVE-2022-31091 < 6.5.8, >= 7.0.0, < 7.4.5 6.5.8, 7.4.5
  3. High · 7.7 CVE-2022-31090 < 6.5.8, >= 7.0.0, < 7.4.5 6.5.8, 7.4.5
  4. High · 7.5 CVE-2022-31042 >= 4.0.0, < 6.5.7, >= 7.0.0, < 7.4.4 6.5.7, 7.4.4
  5. High · 8.0 CVE-2022-29248 < 6.5.6, >= 7.0.0, < 7.4.3 6.5.6, 7.4.3
  6. High · 8.1 CVE-2016-5385 >= 6, < 6.2.1, >= 4.0.0-rc2, < 4.2.4, >= 5, < 5.3.1 6.2.1, 4.2.4, 5.3.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.