No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 09 Oct 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 09 Oct 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sparklemotion
Sparklemotion mechanize |
|
| Vendors & Products |
Sparklemotion
Sparklemotion mechanize |
Fri, 09 Oct 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 08 Oct 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Mechanize sends credential headers to a different scheme or port after a redirect | |
| Weaknesses | CWE-200 CWE-319 CWE-522 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-09T15:06:49.265Z
Reserved: 2026-10-08T17:21:52.975Z
Link: CVE-2026-107714
Updated: 2026-10-09T15:06:45.880Z
Status : Awaiting Analysis
Published: 2026-10-08T22:17:27.003
Modified: 2026-10-09T16:38:57.820
Link: CVE-2026-107714
OpenCVE Enrichment
Updated: 2026-10-09T08:03:06Z