p PatchFirst

CVE-2026-107714

CVE-2026-107714 · Mechanize sends credential headers to a different scheme or port after a redirect

CVSS 5.9 · Medium · EPSS 0.2% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="ruby-mechanize"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

Published
Updated

Stack: system

Affected products and versions

  • mechanize

    Versions
    • < 2.15.0: Affected

    No fix published

  • ruby-mechanize Debian 12

    Versions
    • 2.10.1-1
    • 2.10.1-1.1
    • 2.14.0-1
    • 2.14.0-2
    • 2.14.1-1
    • 2.8.5-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Debian 13

    Versions
    • 2.10.1-1
    • 2.10.1-1.1
    • 2.14.0-1
    • 2.14.0-2
    • 2.14.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Debian 14

    Versions
    • 2.10.1-1
    • 2.10.1-1.1
    • 2.14.0-1
    • 2.14.0-2
    Affected ranges
    • ECOSYSTEM: < 2.14.1-1

    Update to 2.14.1-1

  • ruby-mechanize Ubuntu Pro 16.04 LTS

    Versions
    • 2.7.3-1
    • 2.7.3-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu Pro 18.04 LTS

    Versions
    • 2.7.5-1
    • 2.7.5-2
    • 2.7.5-2ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu Pro 20.04 LTS

    Versions
    • 2.7.6-1
    • 2.7.6-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu 22.04 LTS

    Versions
    • 2.7.7-1
    • 2.7.7-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu 24.04 LTS

    Versions
    • 2.8.5-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu 26.10

    Versions
    • 2.10.1-1.1
    • 2.14.0-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ruby-mechanize Ubuntu 26.04 LTS

    Versions
    • 2.10.1-1.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →