cve.bz

CVE-2026-107714 sparklemotion mechanize: Insufficiently Protected Credentials

5.9 mediumEPSS 0.2%

Medium (5.9) in sparklemotion mechanize. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize::HTTP::Agent#response_redirect treats redirects as same-origin when the host matches without consistently comparing scheme and port. A same-host HTTPS-to-HTTP redirect can send Authorization and Cookie headers over cleartext, while a same-host redirect to another port can send a caller-supplied Cookie header to a different service. Cookies in Mechanize#cookie_jar remain scoped separately; the issue affects caller-supplied headers and can disclose credentials without affecting integrity or availability. This issue is fixed in version 2.14.1.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-319 Cleartext Transmission of Sensitive Information
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A01:2025 Broken Access Control, A04:2025 Cryptographic Failures, A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107714 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107714?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107714?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107714 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sparklemotion mechanize< 2.15.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13ruby-mechanizeno fix listedDEBIAN-CVE-2026-107714
Debian14ruby-mechanize2.14.1-1DEBIAN-CVE-2026-107714
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moreruby-mechanizeno fix listedUBUNTU-CVE-2026-107714

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate information disclosure flaw was found in the mechanize Ruby gem, which is included in the Red Hat 3scale API Management Platform 2.15 system container image. When following HTTP redirects, mechanize (Mechanize::HTTP::Agent#response_redirect) treats a redirect to the same host as same-origin without consistently comparing the scheme and port. A malicious or compromised server can therefore redirect a mechanize client from HTTPS to unencrypted HTTP, or to a different port on the same host, causing caller-supplied Authorization and Cookie headers to be transmitted in cleartext or sent to a different service on that host, exposing authentication credentials and session cookies. Cookies managed by mechanize's own cookie jar remain correctly scoped; the issue affects caller-supplied headers and impacts confidentiality only, with no effect on integrity or availability. Within Red Hat products, this issue only affects the Red Hat 3scale API Management Platform 2.15 update stream, which is out of support scope, so no updated package is planned for it; applications on that stream that send sensitive headers through mechanize requests remain exposed to credential disclosure when following redirects from a malicious server. Red Hat rates this issue moderate (CVSS 5.9), matching the upstream severity, so there is no difference from upstream assessment.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat 3scale API Management Platform 23scale-amp2/system-rhel8Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107714.

Attack patterns (CAPEC)

  • CAPEC-65 Sniff Application Code Likelihood: Low · Severity: High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-117 Interception Likelihood: Low · Severity: Medium
  • CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low
  • CAPEC-477 Signature Spoofing by Mixing Signed and Unsigned Content Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13), CWE-200 (59).

References

Check your stackJSON