CVE-2026-107399: Ruby mechanize · The Mechanize library is used for automating interaction with websites
Affects ruby-mechanizeSource GCVE Database
Not known to be exploited · CVSS 6.8 Medium · fixed in 2.14.1 : update ruby-mechanize when convenient.
Data as of 18 Nov 2026, 04:06 UTC
- Patch
- Available – fixed in 2.14.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10ruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSruby-mechanizepkg:deb/ubuntu/ruby-mechanize?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Mechanize version 2.14.1 or later where this issue is fixed. If upgrading is not immediately possible, ensure that follow_meta_refresh remains disabled (the default setting) and avoid setting sensitive headers in Mechanize#request_headers when follow_meta_refresh is enabled.
Description
The Ruby Mechanize library prior to version 2.14.1 has a vulnerability in its handling of meta refresh redirects across origins when the follow_meta_refresh option is enabled. This flaw allows headers set by the caller, such as bearer tokens or session cookies, to be sent to a different origin, potentially exposing sensitive authentication information. The default configuration is not affected because follow_meta_refresh is disabled by default. The issue is fixed in version 2.14.1.
References
- ubuntu.com/security/CVE-2026-107399 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-107399 (opens in a new tab)
- github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f (opens in a new tab)
- github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa79bc1e16a2c3 (opens in a new tab)
- github.com/sparklemotion/mechanize/pull/676 (opens in a new tab)
- github.com/sparklemotion/mechanize/releases/tag/v2.14.1 (opens in a new tab)
- github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4q9f (opens in a new tab)