CVE-2026-107714mediumCWE-200CWE-319CWE-522

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

Mechanize sends credential headers to a different scheme or port after a 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 5.9epss 0.2%
The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize::HTTP::Agent#response_redirect treats redirects as same-origin when the host matches without consistently comparing scheme and port. A same-host HTTPS-to-HTTP redirect can send Authorization and Cookie headers over cleartext, while a same-host redirect to another port can send a caller-supplied Cookie header to a different service. Cookies in Mechanize#cookie_jar remain scoped separately; the issue affects caller-supplied headers and can disclose credentials without affecting integrity or availability. This issue is fixed in version 2.14.1.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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-107715MEDIUMMechanize sends credential headers to another host after an HTTP redirectEPSS 0.5%CVE-2026-107399MEDIUMMechanize sends credential headers to another origin after a meta refreshEPSS 0.4%