Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
mechanize before 2.14.1 sends credential headers such as Authorization to another host after a redirect when they were set via request_headers= or per-request headers. An attacker who controls a redirect target, such as through an open redirect or a man-in-the-middle position, can capture those headers. Upgrade to mechanize 2.14.1.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.8 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0050, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:21 UTC First seen by agentprime
- 31 Oct 2026, 14:21 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2mwr-xjcg-37j7
- OSV: GHSA-2mwr-xjcg-37j7
- github.com/sparklemotion/mechanize/security/advisories/GHSA-2mwr-xjcg-37j7
- github.com/sparklemotion/mechanize/pull/676
- github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f
- github.com/sparklemotion/mechanize/commit/94e0902867296be804f36eccbb47acf7d5018745
- github.com/sparklemotion/mechanize/commit/ac49abf2869297d83c3b11bbfb8b18e63b588c95
- github.com/sparklemotion/mechanize
- github.com/sparklemotion/mechanize/releases/tag/v2.14.1