The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affected. This issue is fixed in version 2.14.1.
CVE-2026-107715
MEDIUMPre-NVD 6.86.8Trending — 3 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.8Exploit: Elevated riskExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.8
- EG Score
- 6.8MEDIUMlow confidence
- EG Risk
- 47EG Risk 47/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 31st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 8, 2026
Last Modified
October 9, 2026
Advisory Details (6)
Auto-updated Oct 8, 2026🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available
2.14.1
Patch available: sparklemotion/mechanize v2.14.1
https://github.com/sparklemotion/mechanize/releases/tag/v2.14.1github_commit Patch Available
commit ac49abf28692 (sparklemotion/mechanize)
Patch available: sparklemotion/mechanize v2.14.1 (contains commit ac49abf28692)
https://github.com/sparklemotion/mechanize/commit/ac49abf2869297d83c3b11bbfb8b18e63b588c95github_commit Patch Available
commit 94e090286729 (sparklemotion/mechanize)
Patch available: sparklemotion/mechanize v2.14.1 (contains commit 94e090286729)
https://github.com/sparklemotion/mechanize/commit/94e0902867296be804f36eccbb47acf7d5018745github_commit Patch Available
commit 02a1235842d6 (sparklemotion/mechanize)
Patch available: sparklemotion/mechanize v2.14.1 (contains commit 02a1235842d6)
https://github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4fgithub_pr Patch Available
Withhold credential headers across an origin on redirect and meta refresh
Patch available: sparklemotion/mechanize v2.14.1 (PR #676 merged 2026-08-22)
https://github.com/sparklemotion/mechanize/pull/676githubMentions a patch (unverified)🟡 PoC Available
Mechanize sends credential headers to another host after an HTTP redirect · Advisory · sparklemotion/mechanize · GitHub
https://github.com/sparklemotion/mechanize/security/advisories/GHSA-2mwr-xjcg-37j7Vendor Advisories for CVE-2026-107715(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-09 14:45 UTCEG score recompute
- 2026-10-09 13:28 UTCEG score recompute
- 2026-10-08 22:22 UTCEG score recompute
- 2026-10-08 21:29 UTCEG score recompute
- 2026-10-08 21:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-107715?
CVE-2026-107715 is a medium vulnerability published on October 8, 2026. The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#requestheaders= is reapplied by Mechanize::HTTP::Agent#requestaddheaders even after…
When was CVE-2026-107715 disclosed?
CVE-2026-107715 was first published on October 8, 2026, with the most recent update on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-107715 actively exploited?
CVE-2026-107715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107715?
CVE-2026-107715 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-107715?
A fix for CVE-2026-107715 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107715 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107715
Is Your Infrastructure Affected by CVE-2026-107715?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.