Mechanize sends credential headers to another origin after a meta refresh
Summary
| CVE | CVE-2026-107399 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-08 22:17:26 UTC |
| Updated | 2026-10-08 22:17:26 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 6.8 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Problem Types: CWE-200 | CWE-522 | CWE-200 CWE-200: Exposure of Sensitive Information to an Unauthorized Actor | CWE-522 CWE-522: Insufficiently Protected Credentials
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 6.8 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
| 3.1 | CNA | DECLARED | 6.8 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
NoneUser Interaction
NoneScope
ChangedConfidentiality
HighIntegrity
NoneAvailability
NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Sparklemotion | Mechanize | affected < 2.15.0 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa79... | [email protected] | github.com | |
| github.com/sparklemotion/mechanize/pull/676 | [email protected] | github.com | |
| github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4q9f | [email protected] | github.com | |
| github.com/sparklemotion/mechanize/releases/tag/v2.14.1 | [email protected] | github.com | |
| github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba... | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.