CVE-2026-107715mediumCWE-200CWE-522

CVE-2026-107715: medium-severity vulnerability in sparklemotion mechanize

Mechanize sends credential headers to another host after an HTTP redirect

Published · Updated

Follow this CVE+ Monitor mechanize+ Monitor ruby-mechanize

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 6.8epss 0.5%
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected products
sparklemotion · mechanize
Related CVEs — sparklemotion mechanize

In the same product, most dangerous first.

CVE-2021-21289HIGHCommand Injection Vulnerability in MechanizeEPSS 3.5%CVE-2022-31033MEDIUMAuthorization header leak in rubygem MechanizeEPSS 1.5%CVE-2026-107399MEDIUMMechanize sends credential headers to another origin after a meta refreshEPSS 0.4%CVE-2026-107714MEDIUMMechanize sends credential headers to a different scheme or port after a redirectEPSS 0.2%