Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Vyper versions before 0.3.10 evaluate the arguments of the builtins uint256_addmod, uint256_mulmod, ecadd and ecmul out of source order, which matters when one argument has side effects that another depends on. An attacker would need to be able to supply or influence the contract source code being compiled, since the issue arises from how the compiler orders evaluation. The fix is to upgrade to Vyper 0.3.10. As a workaround, avoid side effects in arguments to these builtins, or make sure no other argument depends on them.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.7 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0054, the 45th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-4hg4-9mf5-wxxq
- OSV: GHSA-4hg4-9mf5-wxxq
- github.com/vyperlang/vyper/security/advisories/GHSA-4hg4-9mf5-wxxq
- nvd.nist.gov/vuln/detail/CVE-2023-41052
- github.com/vyperlang/vyper/pull/3583
- github.com/vyperlang/vyper/commit/78fa8dd8f91ba0cb26277eeffb585c68c83e7daa
- github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-168.yaml
- github.com/vyperlang/vyper