Homepage

Information Exposure Affecting ruby-mechanize package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.36% (29th 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-20675255
  • published9 Oct 2026
  • disclosed8 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 8 Oct 2026

NewCVE-2026-107399  (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 applies no origin trust boundary in Mechanize::HTTP::Agent#response_follow_meta_refresh when Mechanize#follow_meta_refresh is enabled. A page containing a meta refresh to another origin causes headers configured through Mechanize#request_headers= to be reapplied to the refresh request, allowing an attacker who controls content in the crawl to capture bearer tokens or session cookies. The default configuration is not affected because follow_meta_refresh is false, and the exposure is limited to caller-supplied default headers. This issue is fixed in version 2.14.1.