Homepage

Information Exposure Affecting ruby-mechanize package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.4% (32nd 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-20675257
  • published9 Oct 2026
  • disclosed8 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 8 Oct 2026

NewCVE-2026-107715  (opens in a new tab)
CWE-200  (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 sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affected. This issue is fixed in version 2.14.1.