CVE-2026-107399: sparklemotion mechanize
Vulnerability summary
CVE-2026-107399 is a medium (CVSS 6.8) vulnerability in sparklemotion mechanize. EPSS estimates a 0.36% chance of exploitation in the next 30 days, higher than 28.8% of scored vulnerabilities.
Timeline
- 08-10-2026PublishedVulnerability first disclosed.
- 14-10-2026Last modifiedVulnerability information updated.
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.
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.36%
Chance of exploitation in the next 30 days
Percentile
29%
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
9 links- github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4q9fX Refsource CONFIRMWEBREPORT
- github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4fX Refsource MISCWEBREPORT
- github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa79bc1e16a2c3X Refsource MISCWEBREPORT