Vulnerability · Published Oct 8, 2026 · Assigned by GitHub_M

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

Medium 5.9

In plain English

A medium-severity information exposure in mechanize from sparklemotion. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 14% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.9Medium
Exploit odds (30 days)0.2%top 86.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12ruby-mechanizeno fix listedDEBIAN-CVE-2026-107714
Debian:13ruby-mechanizeno fix listedDEBIAN-CVE-2026-107714
Debian:14ruby-mechanize2.14.1-1DEBIAN-CVE-2026-107714
Ubuntu:22.04:LTSruby-mechanizeno fix listedUBUNTU-CVE-2026-107714
Ubuntu:24.04:LTSruby-mechanizeno fix listedUBUNTU-CVE-2026-107714
Ubuntu:26.04:LTSruby-mechanizeno fix listedUBUNTU-CVE-2026-107714
Ubuntu:26.10ruby-mechanizeno fix listedUBUNTU-CVE-2026-107714

Affected products (as reported)

VendorProductVersions
sparklemotion mechanize < 2.15.0

Weakness: CWE-200, CWE-319, CWE-522 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

References