AIKIDO-2026-10950
guzzlehttp/guzzle is vulnerable to Exposure of Sensitive Information
53
Medium Risk
This Affects:
guzzlehttp/guzzleTL;DR
When the cURL handler fails while building a response, Guzzle can leave a previous response object attached to the reused handle. If parsing or validation fails on a later request, callers inspecting the thrown exception may see headers or body from an earlier transaction. Before the fix, failed response creation could therefore leak sensitive data from a prior HTTP exchange. The patch clears the in-flight response before parsing and omits stale responses from the error object when creation fails.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range.
Background info
guzzlehttp/guzzle is vulnerable to Exposure of Sensitive Information in versions 7.2.0 - 7.10.0.
How to fix this
Upgrade the guzzlehttp/guzzle library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
SOC 2Compliant
ISO 27001Compliant