CVE-2026-107399mediumCWE-200CWE-522

CVE-2026-107399: falha de média gravidade em sparklemotion mechanize

Mechanize sends credential headers to another origin after a meta refresh

Publicada em · Atualizada em

Seguir esta CVE+ Monitorar mechanize+ Monitorar ruby-mechanize

Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.

13Vexday Risk Score

Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.

ssvc Trackcvss 6.8epss 0.4%
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:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Produtos afetados
sparklemotion · mechanize
CVEs relacionadas — sparklemotion mechanize

No mesmo produto, das mais perigosas para as menos.

CVE-2021-21289HIGHCommand Injection Vulnerability in MechanizeEPSS 3.5%CVE-2022-31033MEDIUMAuthorization header leak in rubygem MechanizeEPSS 1.5%CVE-2026-107715MEDIUMMechanize sends credential headers to another host after an HTTP redirectEPSS 0.5%CVE-2026-107714MEDIUMMechanize sends credential headers to a different scheme or port after a redirectEPSS 0.2%