Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c6rp-p8xm-4q9f | Mechanize sends credential headers to another origin after a meta refresh |
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 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 in version 2.14.1. | |
| Title | Mechanize sends credential headers to another origin after a meta refresh | |
| Weaknesses | CWE-200 CWE-522 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-08T21:24:46.349Z
Reserved: 2026-10-07T21:07:54.989Z
Link: CVE-2026-107399
No data.
Status : Received
Published: 2026-10-08T22:17:26.683
Modified: 2026-10-08T22:17:26.683
Link: CVE-2026-107399
No data.
OpenCVE Enrichment
No data.
Github GHSA