Advisory record · GHSA-g3pv-pj5f-3hfq

mechanize, a library for automatically interacting with HTTP web servers, contains a regular expression that is vulnerable to regular expression denial of service (ReDoS) prior to version 0.4.6. If...

CVSS 7.5 HighCriticalEPSS 0.29 · 98th percentile

Critical, because:

  • CVSS score 7.5 (7.0 or more) and EPSS 0.29 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 Jan 2023, 22:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mechanizePyPI<dd05334448e9f39814bab044d2eaa5ef69b410d6 || <0.4.6dd05334448e9f39814bab044d2eaa5ef69b410d6, 0.4.6
Identifiers
GHSA-g3pv-pj5f-3hfq · CVE-2021-32837 · PYSEC-2023-25
Weakness (CWE)
CWE-1333
Published
17 Jan 2023
Updated
10 Jun 2026

Machine-written summary

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

mechanize versions before 0.4.6 contain a regular expression vulnerable to regular expression denial of service (ReDoS). A malicious web server can send a response that causes mechanize to hang or crash. Upgrade to mechanize 0.4.6, which contains the fix.

Written 10 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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.29, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 17 Jan 2023. New records show when each source confirmed them.

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.