CVE-2026-107399
The Mechanize library is used for automating interaction with …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f
- github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa79bc1e16a2c3
- github.com/sparklemotion/mechanize/pull/676
- github.com/sparklemotion/mechanize/releases/tag/v2.14.1
- github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4q9f
- github.com/advisories/GHSA-c6rp-p8xm-4q9f
- nvd.nist.gov/vuln/detail/CVE-2026-107399
- cve.org/CVERecord?id=CVE-2026-107399
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.