CVE-2026-107715: sparklemotion mechanize
Vulnerability summary
CVE-2026-107715 is a medium (CVSS 6.8) vulnerability in sparklemotion mechanize. EPSS estimates a 0.40% chance of exploitation in the next 30 days, higher than 32.4% of scored vulnerabilities.
Timeline
- 08-10-2026PublishedVulnerability first disclosed.
- 09-10-2026Last modifiedVulnerability information updated.
Description
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.
CVSS metrics
5 scores · 5 sources · 1 version- OSV · DebianEcosystem advisory · calculated6.8MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- OSV · RubygemsEcosystem advisory · calculated6.8MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- NVDNIST6.8MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- OSV · UbuntuEcosystem advisory · calculated6.8MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS trend
Probability
0.40%
Chance of exploitation in the next 30 days
Percentile
32%
Versus all other CVEs
30-day change
Change unavailable
Change unavailable
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-200Exposure of Sensitive Information to an Unauthorized ActorThe product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
- CWE-522Insufficiently Protected CredentialsThe product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Affected systems
Debian1 product
- ruby-mechanizeAll versions (No fix recorded) | < 2.14.1-1
RubyGems1 product
- mechanize< 2.14.1
Sparklemotion1 product
- mechanize< 2.15.0
Ubuntu1 product
- ruby-mechanizeAll versions (No fix recorded)
4 vendors · 4 products
References
10 links- github.com/sparklemotion/mechanize/security/advisories/GHSA-2mwr-xjcg-37j7X Refsource CONFIRMWEBREPORT
- github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4fX Refsource MISCWEBREPORT
- github.com/sparklemotion/mechanize/commit/94e0902867296be804f36eccbb47acf7d5018745X Refsource MISCWEBREPORT
- github.com/sparklemotion/mechanize/commit/ac49abf2869297d83c3b11bbfb8b18e63b588c95X Refsource MISCWEBREPORT