CVE-2026-107715
Mechanize sends credential headers to another host after an HTTP redirect
The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affected. This issue is fixed in version 2.14.1.
| CWE | CWE-200 CWE-522 |
| Vendor | sparklemotion |
| Product | mechanize |
| Published | Oct 8, 2026 |
Get instant alerts for sparklemotion mechanize
Be the first to know when new medium vulnerabilities affecting sparklemotion mechanize are published — delivered to Slack, Telegram or Discord.
CVSS v3 Breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N