Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-c6rp-p8xm-4q9f

Mechanize sends credential headers to another origin after a meta refresh

CVSS 6.8 MediumEPSS 0.0036 · 30th percentile

Published by the GitHub Advisory Database at 8 Oct 2026, 22:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mechanizeRubyGems<2.14.12.14.1
Identifiers
GHSA-c6rp-p8xm-4q9f · CVE-2026-107399
Weakness (CWE)
CWE-200 · CWE-522
Tags
Published
8 Oct 2026
Updated
8 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Mechanize versions before 2.14.1 send headers set through request_headers= to another origin when following a meta refresh, leaking bearer tokens and session cookies. An attacker who can place a meta refresh in a page the agent fetches can capture these credentials, but only when follow_meta_refresh is enabled, which is not the default. Upgrade to mechanize 2.14.1 or later; if you cannot upgrade, keep follow_meta_refresh set to false or avoid putting credentials in request_headers=.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.8 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 30th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:21 UTC First seen by agentprime
  2. 31 Oct 2026, 14:21 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.