Newly released CVEs across every platform — sleek to read, verbose on demand, and served raw as markdown for AI and agent ingestion. Severity reads as depth: the deeper the contact, the graver the threat.
Depth = severity + exploitation
CVE-2020-37288Medium· 3.7Vyper: Return inside for loop more than 1 level deep
GHSA-vg88-3v92-rjx2MediumVyper: Return inside for loop more than 1 level deep
GHSA-4v7v-gqf9-ww2gMediumVyper: Call stack corruption when passing complex type containing non-base type members as argument
GHSA-2r3x-4mrv-mcxfMediumVyper: Memory corruption using function calls within tuples / nested calls
CVE-2025-47285LowVyper's `concat()` builtin may elide side-effects for zero-length arguments
CVE-2025-47774LowVyper's `slice()` may elide side-effects when output length is 0
CVE-2025-21607LowVyper Does Not Check the Success of Certain Precompile Calls
CVE-2024-24563Critical· 9.8Vyper negative array index bounds checks
CVE-2024-24559Low· 3.7Vyper sha3 codegen bug
CVE-2024-24560Low· 3.7Vyper's external calls can overflow return data to return input buffer
CVE-2024-24561Critical· 9.8Vyper's bounds check on built-in `slice()` function can be overflowed
CVE-2024-24567Medium· 4.8Vyper's raw_call `value=` kwargs not disabled for static and delegate calls
CVE-2024-22419High· 7.3concat built-in can corrupt memory in vyper
CVE-2023-46247High· 7.5incorrect storage layout for contracts containing large arrays
CVE-2023-42441Medium· 5.3Vyper has incorrect re-entrancy lock when key is empty string
CVE-2023-41052Medium· 5.3incorrect order of evaluation of side effects for some builtins
CVE-2023-39363High· 8.7Vyper has incorrectly allocated named re-entrancy locks
CVE-2023-32059High· 7.5Vyper vulnerable to incorrect ordering of arguments for kwargs passed to internal calls
CVE-2023-32058High· 7.5Vyper vulnerable to integer overflow in loop
CVE-2023-31146High· 7.5Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment
CVE-2023-30837High· 7.5vyper vulnerable to storage allocator overflow
CVE-2023-30629High· 7.5Incorrect success value returned in vyper
CVE-2021-41121High· 7.5Memory corruption when returning a literal struct with a private call inside of it
CVE-2021-41122Medium· 4.3missing clamps for decimal args in external functions
CVE-2021-48018High· 7.4Storage corruption due to variables overwritten by re-entrancy locks
The beta is over. VulnSea now runs at vulnsea.com, every old beta link redirects to the same page, and your account, API keys and watchlists came with it. Plus a round of hardening, faster pages, and new request limits agents should know about.
A summary of everything that shipped over the last two weeks — the whole corpus is open, agents get change feeds, alias resolution and EPSS movers, and the data now includes CVE.org, vendor CSAF, aggregated exploits and per-source scores.
A step-by-step guide to plugging VulnSea into automated and agentic workflows — poll the delta, triage without burning tokens, match an SBOM, and let an MCP-native model do the reasoning.