All reports
Low

AugAssign evaluation order causing OOB write within the object in Vyper

Affected versions

Version ranges need review.

PyPIvyper
Affected versions
<0.4.1
Fixed version
0.4.1
PyPIvyper
Affected versions
<= 0.4.0
Fixed version
0.4.1

Exploitation

CVE-2025-27105

Probability of exploitation in the next 30 days: 0.57%

FIRST EPSS · 2026-11-21

Description

Vyper handles AugAssign statements by first caching the target location to avoid double evaluation. However, in the case when target is an access to a DynArray and the rhs modifies the array, the cached target will evaluate first, and the bounds check will not be re-evaluated during the write portion of the statement. In other words, the following code

def poc():
    a: DynArray[uint256, 2] = [1, 2]
    a[1] += a.pop()

is equivalent to:

def poc():
    a: DynArray[uint256, 2] = [1, 2]
    a[1] += a[len(a) - 1]
    a.pop()

rather than:

def poc():
    a: DynArray[uint256, 2] = [1, 2]
    s: uint256 = a[1]
    t: uint256 = a.pop()
    a[1] = s + t  # reverts due to oob access

Links