vyper performs double eval of raw_args in create_from_blueprint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2024-32647: 0.46% estimated exploitation activity in the next 30 days; percentile 39.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Using the createfromblueprint builtin can result in a double eval vulnerability when rawargs=True and the args argument has side-effects. A contract search was performed and no vulnerable contracts were found in production. In particular, the rawargs variant of createfromblueprint was not found to be used in production. Details It can be seen that the buildcreateIR function of the createfromblueprint builtin doesn't cache the mentioned args argument to the stack: https://github.com/vyperlang/vyper/blob/cedf7087e68e67c7bfbd47ae95dcb16b81ad2e02/vyper/builtins/functions.py#L1847 As such, it can be evaluated multiple times (instead of retrieving the value from the stack). PoC The vulnerability is demonstrated in the following boa test: The output of c2.deployed() is 2 although create was called only once and the value was initialized to 0. Patches Patched in https://github.com/vyperlang/vyper/pull/3976. Impact No vulnerable production contracts were found. Additionally, double…

Published by the source

25 Apr 2024, 19:50 UTC

Last modified by the source

10 Jun 2026, 17:14 UTC

Source last checked

26 Oct 2026, 13:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3whq-64q2-qfj6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3whq-64q2-qfj6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32647

Advisory: vyper performs double eval of raw_args in create_from_blueprint
IDs: CVE-2024-32647, GHSA-3whq-64q2-qfj6
Record: https://patchnext.com/advisories/cve-2024-32647 (revision 2, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vyper 0.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI vyper: affected < 0.4.0; fixed in 0.4.0

## Suggested inspection (read-only)
- `python -m pip show vyper`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vyper.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3whq-64q2-qfj6 (OSV record GHSA-3whq-64q2-qfj6 lists affected ranges: PyPI vyper >=0 <0.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-3whq-64q2-qfj6 (GitHub-reviewed advisory GHSA-3whq-64q2-qfj6 lists affected ranges: PyPI vyper >=0 <0.4.0)

Commands are suggestions: review each one before running it.