vyper performs incorrect topic logging in raw_log

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-32645: 0.46% estimated exploitation activity in the next 30 days; percentile 39.56 (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 Incorrect values can be logged when rawlog builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in production. In particular, no uses of rawlog() were found at all in production; it is apparently not a well-known function. Details The buildIR function of the RawLog class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics. PoC Patches Fixed in https://github.com/vyperlang/vyper/pull/3977. Impact Incorrect values can be logged which may result in unexpected behavior in client-side applications relying on these logs.

Published by the source

25 Apr 2024, 19:53 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-xchq-w5r3-4wg3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xchq-w5r3-4wg3

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

# Patch Next advisory brief: CVE-2024-32645

Advisory: vyper performs incorrect topic logging in raw_log
IDs: CVE-2024-32645, GHSA-xchq-w5r3-4wg3
Record: https://patchnext.com/advisories/cve-2024-32645 (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-xchq-w5r3-4wg3 (OSV record GHSA-xchq-w5r3-4wg3 lists affected ranges: PyPI vyper >=0 <0.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-xchq-w5r3-4wg3 (GitHub-reviewed advisory GHSA-xchq-w5r3-4wg3 lists affected ranges: PyPI vyper >=0 <0.4.0)

Commands are suggestions: review each one before running it.