AugAssign evaluation order causing OOB write within the object in Vyper
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| vyperlang | vyper | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-4283 | AugAssign evaluation order causing OOB write within the object in Vyper |
Github GHSA |
GHSA-4w26-8p97-f4jp | AugAssign evaluation order causing OOB write within the object in Vyper |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.570% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vyperlang
Vyperlang vyper |
|
| CPEs | cpe:2.3:a:vyperlang:vyper:*:*:*:*:*:python:*:* | |
| Vendors & Products |
Vyperlang
Vyperlang vyper |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vyper is a Pythonic Smart Contract Language for the EVM. 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. This issue has been addressed in version 0.4.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability. | |
| Title | AugAssign evaluation order causing OOB write within the object in Vyper | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV4_0
|