PYSEC-2025-31
Vulnerability from pysec - Published: 2025-02-21 22:15 - Updated: 2025-04-09 17:27
VLAI?
Details
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.
Impacted products
| Name | purl | vyper | pkg:pypi/vyper |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "vyper",
"purl": "pkg:pypi/vyper"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.4.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0b1",
"0.1.0b10",
"0.1.0b11",
"0.1.0b12",
"0.1.0b13",
"0.1.0b14",
"0.1.0b15",
"0.1.0b16",
"0.1.0b17",
"0.1.0b2",
"0.1.0b3",
"0.1.0b4",
"0.1.0b5",
"0.1.0b6",
"0.1.0b7",
"0.1.0b8",
"0.1.0b9",
"0.2.1",
"0.2.10",
"0.2.11",
"0.2.12",
"0.2.13",
"0.2.14",
"0.2.15",
"0.2.16",
"0.2.2",
"0.2.3",
"0.2.4",
"0.2.5",
"0.2.6",
"0.2.7",
"0.2.8",
"0.2.9",
"0.3.0",
"0.3.1",
"0.3.10",
"0.3.10rc1",
"0.3.10rc2",
"0.3.10rc3",
"0.3.10rc4",
"0.3.10rc5",
"0.3.2",
"0.3.3",
"0.3.4",
"0.3.5",
"0.3.6",
"0.3.7",
"0.3.8",
"0.3.9",
"0.4.0",
"0.4.0b1",
"0.4.0b2",
"0.4.0b3",
"0.4.0b4",
"0.4.0b5",
"0.4.0b6",
"0.4.0rc1",
"0.4.0rc2",
"0.4.0rc3",
"0.4.0rc4",
"0.4.0rc5",
"0.4.0rc6",
"0.4.1b1",
"0.4.1b2",
"0.4.1b3",
"0.4.1b4",
"0.4.1rc1",
"0.4.1rc2",
"0.4.1rc3"
]
}
],
"aliases": [
"CVE-2025-27105",
"GHSA-4w26-8p97-f4jp"
],
"details": "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.",
"id": "PYSEC-2025-31",
"modified": "2025-04-09T17:27:28.116292+00:00",
"published": "2025-02-21T22:15:13+00:00",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-4w26-8p97-f4jp"
},
{
"type": "EVIDENCE",
"url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-4w26-8p97-f4jp"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…