Skip to main content

CVE-2026-107399: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in sparklemotion mechanize

0
Medium
VulnerabilityCVE-2026-107399cvecve-2026-107399cwe-200cwe-522
Published: 10/08/2026 (10/08/2026, 21:24:46 UTC)
Source: CVE Database V5
Vendor/Project: sparklemotion
Product: mechanize

Description

A vulnerability in the Mechanize library prior to version 2.14.1 allows exposure of sensitive information due to improper handling of meta refresh requests across origins. When the follow_meta_refresh feature is enabled, headers set by the user are reapplied to requests following a meta refresh to a different origin, potentially leaking bearer tokens or session cookies. The default configuration is not affected since follow_meta_refresh is disabled by default. This issue is fixed in version 2.14.1.

CVSS v3.1

Score 6.8medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected software

sparklemotion

mechanize

Affected versions
<2.15.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/08/2026, 22:35:38 UTC

Technical Analysis

Mechanize versions before 2.14.1 do not enforce an origin trust boundary in the response_follow_meta_refresh method when follow_meta_refresh is enabled. This causes user-configured request headers, including sensitive authentication tokens, to be sent to a different origin during a meta refresh redirect. An attacker controlling content in the crawl could exploit this to capture bearer tokens or session cookies. The vulnerability is resolved in Mechanize 2.14.1.

Potential Impact

The vulnerability allows unauthorized actors to obtain sensitive authentication information such as bearer tokens or session cookies if the follow_meta_refresh feature is enabled and custom headers containing such tokens are set. The default Mechanize configuration is not vulnerable because follow_meta_refresh is disabled by default. There is no impact on integrity or availability, only confidentiality.

Mitigation Recommendations

Upgrade Mechanize to version 2.14.1 or later where this issue is fixed. If upgrading is not immediately possible, ensure that follow_meta_refresh remains disabled (the default setting) and avoid setting sensitive headers in request_headers when enabling follow_meta_refresh.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-10-07T21:07:54.989Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac80c6f2cdf04f6563805bf

Added to database: 10/08/2026, 21:34:39 UTC

Last enriched: 10/08/2026, 22:35:38 UTC

Last updated: 10/08/2026, 23:48:17 UTC

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses