cve.bz

CVE-2026-107715 sparklemotion mechanize: Insufficiently Protected Credentials

6.8 mediumEPSS 0.5%Fix available

Medium (6.8) in sparklemotion mechanize. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in mechanize 2.14.1.

On this page
The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affected. This issue is fixed in version 2.14.1.

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · 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-522 Insufficiently Protected Credentials
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107715 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107715?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107715?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-107715 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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2mwr-xjcg-37j7RubyGemsmechanize<2.14.12.14.1

Linux distributions

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

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-impact information disclosure flaw was found in the mechanize Ruby gem, which is used in the Red Hat 3scale API Management Platform 2 system container. When mechanize follows an HTTP redirect that crosses to a different host, it fails to strip caller-supplied credential headers: headers set through Mechanize#request_headers= or the per-request headers argument are reapplied to the redirected request, and the protected header lists omit Proxy-Authorization and Cookie2. A remote attacker who controls the redirect target can therefore capture sensitive authentication data, such as bearer tokens and session cookies, supplied with the original request. Mechanize's cookie jar (Mechanize#cookie_jar) and HTTP authentication store (Mechanize::HTTP::AuthStore) are not affected. Red Hat rates this flaw as MODERATE, consistent with the upstream severity. Within the Red Hat portfolio, the only affected product is Red Hat 3scale API Management Platform 2 (the 3scale-amp2 system container); its affected update stream is out of support scope, so no fix is currently planned for it. The residual risk is limited to applications that pass credential headers to mechanize requests that may be redirected to a host controlled by an attacker.

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-107715.

Attack patterns (CAPEC)

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