What’s Vulnerable › Vulnerabilities

CVE-2026-107714: Mechanize sends credential headers to a different scheme or port after a redirect

• Severity: medium (CVSS 5.9 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-10-08 · updated 2026-10-09
• Weakness: CWE-200

Description

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.

Affected products

• sparklemotion mechanize: before 2.15.0

References

• https://github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f
• https://github.com/sparklemotion/mechanize/commit/2f97fe358a91928e5e48221f2ec5cb50fa1a43ba
• https://github.com/sparklemotion/mechanize/pull/676
• https://github.com/sparklemotion/mechanize/releases/tag/v2.14.1
• https://github.com/sparklemotion/mechanize/security/advisories/GHSA-5jgv-wc2m-xv99

Get alerted when CVE-2026-107714 or the next vulnerability affects your stack