CVE-2026-107714 json
Mechanize sends credential headers to a different scheme or port after a redirect
published last mo. modified last mo. also EUVD-2026-95320
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- mechanize_project mechanize 2.15.0
- ruby-mechanize Debian 14 2.14.1-1
debian advisories DEBIAN-CVE-2026-107714
Is CVE-2026-107714 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-107714 updated cvss 5.9
mechanize: mechanize: Information disclosure via improper redirect scheme and port handling
-
Red Hat 3scale API Management Platform 2 3scale-amp2/system-rhel8affected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- sparklemotion mechanize
Classification
References
- github.com /sparklemotion/mechanize/pull/676
- github.com /sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f
- github.com /sparklemotion/mechanize/commit/2f97fe358a91928e5e48221f2ec5cb50fa1a43ba
- github.com /sparklemotion/mechanize/security/advisories/GHSA-5jgv-wc2m-xv99
- github.com /sparklemotion/mechanize/releases/tag/v2.14.1
Sources
- CVE List CVE-2026-107714
- NVD CVE-2026-107714
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.