{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "source": "REFERENCES"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f"
            },
            {
              "fixed": "84c74df87d15f5d119df268ba6aa79bc1e16a2c3"
            },
            {
              "fixed": "a40941e3a29720850e5b6158340d78e239b4f9a5"
            }
          ],
          "repo": "https://github.com/sparklemotion/mechanize",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-c6rp-p8xm-4q9f"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-200",
      "CWE-522"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/107xxx/CVE-2026-107399.json",
    "unresolved_ranges": [
      {
        "extracted_events": [
          {
            "fixed": "2.15.0"
          }
        ],
        "source": "AFFECTED_FIELD"
      }
    ]
  },
  "details": "The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agent#response_follow_meta_refresh when Mechanize#follow_meta_refresh is enabled. A page containing a meta refresh to another origin causes headers configured through Mechanize#request_headers= to be reapplied to the refresh request, allowing an attacker who controls content in the crawl to capture bearer tokens or session cookies. The default configuration is not affected because follow_meta_refresh is false, and the exposure is limited to caller-supplied default headers. This issue is fixed in version 2.14.1.",
  "id": "CVE-2026-107399",
  "modified": "2026-10-11T02:30:52.180698733Z",
  "published": "2026-10-08T21:24:46.349Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/sparklemotion/mechanize/releases/tag/v2.14.1"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/107xxx/CVE-2026-107399.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/sparklemotion/mechanize/security/advisories/GHSA-c6rp-p8xm-4q9f"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107399"
    },
    {
      "type": "FIX",
      "url": "https://github.com/sparklemotion/mechanize/commit/02a1235842d6eda8d4a5a3d8f13aba2cecf52e4f"
    },
    {
      "type": "FIX",
      "url": "https://github.com/sparklemotion/mechanize/commit/84c74df87d15f5d119df268ba6aa79bc1e16a2c3"
    },
    {
      "type": "FIX",
      "url": "https://github.com/sparklemotion/mechanize/pull/676"
    }
  ],
  "schema_version": "1.9.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Mechanize sends credential headers to another origin after a meta refresh"
}