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

> Mechanize leaks credentials and cookies to insecure schemes or ports during redirects, exposing sensitive data to attackers.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107714, GHSA-5jgv-wc2m-xv99, UBUNTU-CVE-2026-107714

## What is CVE-2026-107714?

CVE-2026-107714 is a medium-severity vulnerability in sparklemotion mechanize, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-107714?


## How do I fix CVE-2026-107714?

Upgrade to a fixed version.

## Is CVE-2026-107714 being exploited?

There is no known exploitation of CVE-2026-107714 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107714 and fix it if it is affected.

What it is: CVE-2026-107714 is a medium-severity vulnerability in sparklemotion mechanize, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107714 in the wild and no public exploit code.

Affected product: sparklemotion mechanize. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107714/ (Markdown: https://insights.sbomify.com/CVE-2026-107714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107714
- OSV: https://osv.dev/vulnerability/CVE-2026-107714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107714/
Summaries are generated and may contain mistakes; the official description above is the record.