PT-2026-115982
Published
2026-10-06
·
Updated
2026-10-06
Description by
CVSS 4.0
6.3
MediumMetricsAV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
VVE-2020-0002
Earlier today, we received a responsible disclosure of a potential issue from @michwill (developer of @curvefi) for Vyper users who use return statements inside for loops of nested internal calls. Returning inside a for loop causes an invalid jump dest, reverting the transaction unnecessarily.
MWE:
python
@internal
def baz():
for i in range(1):
return # Stack underflow happens here
@internal
def bar():
self. baz()
@external
def foo():
self. bar()Impact
Impact is minor, it is unlikely a user would encounter this problem unless they were working with nested calls, and return statements inside calls. Even in that scenario, you would encounter a revert which should be noticeable with adequate testing. In limited circumstances, this could cause a DoS attack for public contracts under certain conditions.
Patches
Fixed in https://github.com/vyperlang/vyper/pull/2110. Please upgrade to Vyper 0.2.3
Workarounds
Not returning inside a for loop nested 2+ internal calls deep works as is:
python
@internal
def baz():
for i in range(1):
pass
return # This works fine
@internal
def bar():
self. baz()
@external
def foo():
self. bar()For more information
If you have any questions or comments about this advisory:
- Chat with us in our gitter
- Open an issue in https://github.com/vyperlang/vyper
- Email us at security@vyperlang.org
Found an issue in the description? Have something to add? Feel free to write us 👾