# eth-abi is vulnerable to recursive DoS Advisory record · `GHSA-3qwc-47jf-5rf7` - **Identifiers:** `GHSA-3qwc-47jf-5rf7` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **Weakness (CWE):** [CWE-1285](https://cwe.mitre.org/data/definitions/1285.html) - **Tags:** [CWE-1285](https://agentprime.io/advisories/tag/cwe-1285.md) - **Published:** 5 Mar 2024 - **Updated:** 1 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 5 Mar 2024, 14:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `eth-abi` (PyPI): affected `<5.0.1`; fixed in `5.0.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > eth-abi versions before 5.0.1 are vulnerable to a recursive denial-of-service issue. The source gives few details: it describes a recursive pointer problem and refers to a related advisory, but does not say what input triggers it or what the impact is beyond denial of service. Upgrade to eth-abi 5.0.1, which is listed as the fixed version. Written 5 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 No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** No score. ## Timeline - 31 Oct 2026, 14:38 UTC: First seen by agentprime - 31 Oct 2026, 14:38 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3qwc-47jf-5rf7) ## Sources - [GitHub Advisory Database: GHSA-3qwc-47jf-5rf7](https://github.com/advisories/GHSA-3qwc-47jf-5rf7) - [OSV: GHSA-3qwc-47jf-5rf7](https://osv.dev/vulnerability/GHSA-3qwc-47jf-5rf7) - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .