{"answers":{"affected":"3 open source packages ship an affected version, including vyper.","exploited":"There is no known exploitation of CVE-2025-47285 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47285 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47285 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-47285 and fix it if it is affected.\n\nWhat it is: CVE-2025-47285 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-47285 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-47285/ (Markdown: https://insights.sbomify.com/CVE-2025-47285/index.md)","id":"CVE-2025-47285","markdown":"https://insights.sbomify.com/CVE-2025-47285/index.md","name":"CVE-2025-47285","record":{"aliases":["GHSA-qhr6-mgqr-mchm","PYSEC-2026-2029"],"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 zero-length concat arguments, 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, `concat()` may skip evaluation of side effects when the length of an argument is zero. This is due to a fastpath in the implementation which skips evaluation of argument expressions when their length is zero. In practice, it would be very unusual in user code to construct zero-length bytestrings using an expression with side-effects, since zero-length bytestrings are typically constructed with the empty literal `b\"\"`; the only way to construct an empty bytestring which has side effects would be with the ternary operator introduced in v0.3.8, e.g. `b\"\" if self.do_some_side_effect() else b\"\"`. The fix is available in pull request 4644 and expected to be part of the 0.4.2 release. As a workaround, don't have side effects in expressions which construct zero-length bytestrings.","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 `concat()` builtin may elide side-effects for zero-length arguments","id":"CVE-2025-47285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Combodo iTop vulnerable to Remote Code Execution in the backup creation functionality","id":"CVE-2025-47286"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":null,"source":"GHSA-qhr6-mgqr-mchm"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":"pkg:pypi/vyper","source":"GHSA-qhr6-mgqr-mchm"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.4.2rc1"],"package":"vyper","purl":"pkg:pypi/vyper","source":"PYSEC-2026-2029"}],"prev":{"headline":"Gardener vulnerable to metadata injection for a project secret that can lead to privilege escalation","id":"CVE-2025-47284"},"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 zero-length concat arguments, potentially altering smart contract logic execution.","url":"https://insights.sbomify.com/CVE-2025-47285/"}