p PatchFirst

PatchFirst · Latest vulnerabilities

mechanize vulnerabilities

Vulnerabilities published for mechanize in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. CVE-2026-107715

    Medium · CVSS 6.8EPSS 0.5%Fix available

    Mechanize sends credential headers to another host after an HTTP redirect

    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 affect

    • Update to 2.14.1
    Published Updated
  2. CVE-2026-107399

    Medium · CVSS 6.8EPSS 0.36%Fix available

    Mechanize sends credential headers to another origin after a meta refresh

    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

    • Update to 2.14.1
    Published Updated
  3. CVE-2022-31033

    Medium · CVSS 5.9EPSS 1.52%Fix available

    Authorization header leak in rubygem Mechanize

    The Mechanize library is used for automating interaction with websites. Mechanize automatically stores and sends cookies, follows redirects, and can follow links and submit forms. In versions prior to 2.8.5 the Authorization header is leaked after a redirect to a different port on the same site. Users are advised to upgrade to Mechanize v2.8.5 or later. There are no known workarounds for this issue.

    • Update to 2.8.5
    Published Updated
  4. CVE-2021-21289

    High · CVSS 7.4EPSS 3.55%Fix available

    Command Injection Vulnerability in Mechanize

    Mechanize is an open-source ruby library that makes automated web interaction easy. In Mechanize from version 2.0.0 and before version 2.7.7 there is a command injection vulnerability. Affected versions of mechanize allow for OS commands to be injected using several classes' methods which implicitly use Ruby's Kernel.open method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls: Mechanize::CookieJar#load, Mechanize::CookieJar#save_as, Mechanize#download, Mechanize::Download#save, Mechanize::File#save, and Mechanize::FileResponse#read_body. This is fixed in version 2.7.7.

    • Update to 2.7.7
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →