CVE-2025-47774: Vyper Vyper's `slice()` May Elide Side-effects Vulnerability
LOWCVE-2025-47774 is a LOW vyper's `slice()` may elide side-effects vulnerability (CWE-691: Insufficient Control Flow Management) affecting Vyper libraries in the PyPI ecosystem. The issue involves vyper's `slice()` may elide side-effects when output length is 0. Remediation is available in the latest vendor maintenance releases.
CVE-2025-47774 at a Glance
How to Fix CVE-2025-47774
To remediate this vulnerability, upgrade all affected Vyper dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install vyper>=Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show vyper
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-47774, inspect your installed packages using pip:
pip show vyper
Analyze the terminal output to locate any version of Vyper in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The pip show vyper command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-691: Insufficient Control Flow Management, where the code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways. In Vyper, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-47774 Affected Vyper Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
vyper
|
PyPI |
≤ 0.4.2rc1
|
|
References
Frequently Asked Questions
What is CVE-2025-47774?
Which Vyper versions are affected?
What version fixes CVE-2025-47774?
Is vyper affected?
What CWE is associated with CVE-2025-47774?
How can I check PyPI dependencies for CVE-2025-47774?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3vcg-j39x-cwfm",
"modified" : "2025-05-16T14:13:29Z",
"published" : "2025-05-16T14:13:29Z",
"aliases" : [ "CVE-2025-47774" ],
"summary" : "Vyper's `slice()` may elide side-effects when output length is 0",
"details" : "### Impact\nthe `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `<address>.code`). the reason is that for these source locations, the check that `length >= 1` is skipped:\nhttps://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L315-L319\n\nthe result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0:\nhttps://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/codegen/core.py#L189-L191\n\nthe impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`.\n\nthe following example illustrates how the issue would look in user code\n```vyper\ncounter: public(uint256)\n\n@external\ndef test() -> Bytes[10]:\n b: Bytes[10] = slice(msg.data, self.side_effect(), 0)\n return b\n\ndef side_effect() -> uint256:\n self.counter += 1\n return 0\n```\n\nthe severity assigned is low, since this is not a very useful pattern and unlikely to be found in user code.\n\n### Patches\n\nthe fix is tracked in https://github.com/vyperlang/vyper/pull/4645, which disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### References\n_Are there any links users can visit to find out more?_",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "vyper"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.4.2rc1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/vyperlang/vyper/security/advisories/GHSA-3vcg-j39x-cwfm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-47774"
}, {
"type" : "WEB",
"url" : "https://github.com/vyperlang/vyper/pull/4645"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/vyperlang/vyper"
}, {
"type" : "WEB",
"url" : "https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L315-L319"
}, {
"type" : "WEB",
"url" : "https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/codegen/core.py#L189-L191"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-691" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-05-16T14:13:29Z",
"nvd_published_at" : "2025-05-15T18:15:38Z"
}
}