{"answers":{"affected":"3 open source packages ship an affected version, including vyper.","exploited":"There is no known exploitation of CVE-2025-47774 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47774 is a low-severity vulnerability in vyperlang vyper, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47774 and fix it if it is affected.\n\nWhat it is: CVE-2025-47774 is a low-severity vulnerability in vyperlang vyper, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-47774 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vyper (PyPI): affected all versions up to 0.4.2rc1; no fix listed\n- vyper (PyPI): affected all versions up to 0.4.2rc1; no fix listed\n- vyper (PyPI): affected all versions up to 0.4.2rc1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47774/ (Markdown: https://insights.sbomify.com/CVE-2025-47774/index.md)","id":"CVE-2025-47774","markdown":"https://insights.sbomify.com/CVE-2025-47774/index.md","name":"CVE-2025-47774","record":{"aliases":["GHSA-3vcg-j39x-cwfm","PYSEC-2026-2028"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Vyper compiler","requires_auth":"none","summary":"Vyper compiler may skip side effects in slice operations with zero length, potentially altering smart contract logic execution.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-691","name":"Insufficient Control Flow Management"}],"description":"Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `\u003caddress\u003e.code`). The reason is that for these source locations, the check that `length \u003e= 1` is skipped. The 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. The 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)`. The fix in pull request 4645 disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory. The fix is expected to be part of version 0.4.2.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Vyper's `slice()` may elide side-effects when output length is 0","id":"CVE-2025-47774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"Bullfrog's DNS over TCP bypasses domain filtering","id":"CVE-2025-47775"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":null,"source":"GHSA-3vcg-j39x-cwfm"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":"pkg:pypi/vyper","source":"GHSA-3vcg-j39x-cwfm"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":"pkg:pypi/vyper","source":"PYSEC-2026-2028"}],"prev":{"headline":"Combodo iTop has XSS vulnerability in /pages/ajax.render.php","id":"CVE-2025-47773"},"products":["vyper"],"published":"2025-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["vyperlang"]},"summary":"Vyper compiler may skip side effects in slice operations with zero length, potentially altering smart contract logic execution.","url":"https://insights.sbomify.com/CVE-2025-47774/"}