# CVE-2024-32647: vyper performs double eval of raw_args in create_from_blueprint

Source: https://junglewise.ai/threats/cve-2024-32647-vyper-performs-double-eval-of-raw-args-in-create-from-blueprint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-04-25  
License: CC BY 4.0 with a link back

CVE-2024-32647 · Severity: low · CVSS 3.1 · Published 2024-04-25

Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, using the `create_from_blueprint` builtin can result in a double eval vulnerability when `raw_args=True` and the `args` argument has side-effects. It can be seen that the `_build_create_IR` function of the `create_from_blueprint` builtin doesn't cache the mentioned `args` argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low. As of time of publication, no fixed versions exist.

Technologies: [vyper (PyPI)](https://junglewise.ai/threats/technologies/vyper). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2024-32647 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-32647 being exploited in the wild.

**How severe is CVE-2024-32647?** Low severity, with a CVSS score of 3.1, published 25 April 2024.

**Which products and versions are affected?** vyper (PyPI) ECOSYSTEM:introduced=0,fixed=0.4.0.

**Is there a fix for CVE-2024-32647?** Yes. vyper (PyPI): upgrade to 0.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-32647?** Check whether you run vyper (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- vyper (PyPI): upgrade to 0.4.0 or later

  ```sh
  pip install "vyper>=0.4.0"
  ```


## Affected products

- vyper (PyPI) ECOSYSTEM:introduced=0,fixed=0.4.0

## Identifiers

- CVE-2024-32647
- GHSA-3whq-64q2-qfj6
- PYSEC-2024-208

## Related threats

- [Vyper memory corruption in nested function calls and tuples](https://junglewise.ai/threats/vyper-memory-corruption-using-function-calls-within-tuples-nested-calls-c0689acb)
- [Vyper stack corruption in complex type argument passing](https://junglewise.ai/threats/vyper-call-stack-corruption-when-passing-complex-type-containing-non-3deb0c30)
- [Vyper return statement in nested for loops causes revert](https://junglewise.ai/threats/vyper-return-inside-for-loop-more-than-1-level-deep-ee8a193d)
- [PYSEC-2026-2028 - Vyper's `slice()` may elide side-effects when output length is 0](https://junglewise.ai/threats/cve-2025-47774-vyper-s-slice-may-elide-side-effects-when-output-length-is-0)
- [PYSEC-2026-2029 - Vyper's `concat()` builtin may elide side-effects for zero-length arguments](https://junglewise.ai/threats/cve-2025-47285-vyper-s-concat-builtin-may-elide-side-effects-for-zero-length)
