{"answers":{"affected":"2 open source packages ship an affected version, including mechanize.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107715 exists.","fix":"Upgrade mechanize to 2.14.1 or later.","what":"CVE-2026-107715 is a medium-severity vulnerability in sparklemotion mechanize, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-107715 and fix it if it is affected.\n\nWhat it is: CVE-2026-107715 is a medium-severity vulnerability in sparklemotion mechanize, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107715 exists.\n\nAffected packages and fixed versions:\n- mechanize (RubyGems): affected all versions; fixed in 2.14.1\n- mechanize (RubyGems): affected all versions; fixed in 2.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-107715/ (Markdown: https://insights.sbomify.com/CVE-2026-107715/index.md)","id":"CVE-2026-107715","markdown":"https://insights.sbomify.com/CVE-2026-107715/index.md","name":"CVE-2026-107715","record":{"aliases":["DEBIAN-CVE-2026-107715","GHSA-2mwr-xjcg-37j7","UBUNTU-CVE-2026-107715"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby web automation library","requires_auth":"none","summary":"Mechanize leaks credential headers to attacker-controlled hosts during redirects, allowing capture of bearer tokens or session cookies.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Mechanize sends credential headers to another host after an HTTP redirect","id":"CVE-2026-107715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"Banks: Symlink traversal and arbitrary file disclosure/overwrite in DirectoryPromptRegistry","id":"CVE-2026-107716"},"packages":[{"ecosystem":"RubyGems","fixed":["2.14.1"],"introduced":["0"],"last_affected":[],"package":"mechanize","purl":null,"source":"GHSA-2mwr-xjcg-37j7"},{"ecosystem":"RubyGems","fixed":["2.14.1"],"introduced":["0"],"last_affected":[],"package":"mechanize","purl":"pkg:gem/mechanize","source":"GHSA-2mwr-xjcg-37j7"}],"prev":{"headline":"Mechanize sends credential headers to a different scheme or port after a redirect","id":"CVE-2026-107714"},"products":["mechanize"],"published":"2026-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-09","vendors":["sparklemotion"]},"summary":"Mechanize leaks credential headers to attacker-controlled hosts during redirects, allowing capture of bearer tokens or session cookies.","url":"https://insights.sbomify.com/CVE-2026-107715/"}