Homepage

Information Exposure Affecting ruby-mechanize package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.23% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-RUBYMECHANIZE-20675256
  • published9 Oct 2026
  • disclosed8 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 8 Oct 2026

NewCVE-2026-107714  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-319  (opens in a new tab)
CWE-522  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest ruby-mechanize.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby-mechanize package and not the ruby-mechanize package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.