CVE-2022-31043 is a high-severity incorrect authorization vulnerability in guzzlehttp/guzzle (composer), affecting versions >= 7.0.0, < 7.4.4. It is fixed in 7.4.4, 6.5.7.
Impact Authorization 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, we should not forward the Authorization header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, https to http downgrades did not result in the Authorization header being removed, only changes to the host. 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 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.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2022-31043 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (7.4.4, 6.5.7). Upgrading removes the vulnerable code path.
composer
guzzlehttp/guzzle (>= 7.0.0, < 7.4.4)guzzlehttp/guzzle (>= 4.0.0, < 6.5.7)guzzlehttp/guzzle → 7.4.4 (composer)guzzlehttp/guzzle → 6.5.7 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2022-31043 is reachable in your applications. Explore open-source security for your team.
See if CVE-2022-31043 is reachable in your applications. Get a demo
Upgrade the following packages to resolve this vulnerability:
guzzlehttp/guzzle to 7.4.4 or laterguzzlehttp/guzzle to 6.5.7 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2022-31043 is a high-severity incorrect authorization vulnerability in guzzlehttp/guzzle (composer), affecting versions >= 7.0.0, < 7.4.4. It is fixed in 7.4.4, 6.5.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
CVE-2022-31043 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
guzzlehttp/guzzle (composer) versions >= 7.0.0, < 7.4.4 is affected.
Yes. CVE-2022-31043 is fixed in 7.4.4, 6.5.7. Upgrade to this version or later.
Whether CVE-2022-31043 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
guzzlehttp/guzzle to 7.4.4 or laterguzzlehttp/guzzle to 6.5.7 or later