Skip to main content

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

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

Description

CVE-2026-107714 is a vulnerability in the sparklemotion mechanize library prior to version 2.14.1. The issue arises from how the library treats HTTP redirects as same-origin based only on host matching, without consistently verifying the scheme and port. This can cause sensitive Authorization and Cookie headers to be sent over unencrypted HTTP or to unintended services on different ports, potentially exposing credentials. The vulnerability affects caller-supplied headers but does not impact integrity or availability. The issue is fixed in version 2.14.1.

CVSS v3.1

Score 5.9medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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:34 UTC

Technical Analysis

The Mechanize library automates website interactions. Before version 2.14.1, its HTTP agent component incorrectly treats redirects as same-origin if the host matches, ignoring differences in scheme (HTTPS vs HTTP) and port. This flaw allows a same-host HTTPS-to-HTTP redirect to leak Authorization and Cookie headers over cleartext, and a redirect to a different port on the same host to send caller-supplied Cookie headers to unintended services. Cookies managed by Mechanize's cookie jar remain properly scoped, so the vulnerability specifically concerns caller-supplied headers. This can lead to exposure of sensitive credentials without affecting data integrity or service availability. The vulnerability is addressed in version 2.14.1.

Potential Impact

An attacker could exploit this vulnerability to intercept sensitive Authorization and Cookie headers by causing redirects from HTTPS to HTTP or to different ports on the same host. This exposure can lead to credential disclosure. The flaw does not compromise data integrity or availability but risks unauthorized information disclosure.

Mitigation Recommendations

Upgrade to mechanize version 2.14.1 or later, where this issue is fixed. No other mitigation is necessary as the vulnerability is resolved in the official patch.

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-08T17:21:52.975Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac80c6f2cdf04f6563805c1

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

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

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

Views: 10

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