CVE-2025-47285: Vyper's `concat()` builtin may elide side-effects for zero-length arguments

Published May 15, 2025
·
Updated

Impact 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: https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L560-L562

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.dosomesideeffect() else b"".

the following example demonstrates how the issue would look in user code vyper counter: public(uint256)

@external def test() -> Bytes[256]: a: Bytes[256] = concat(b"" if self.sideeffect() else b"", b"aaaa") return a

def sideeffect() -> bool: self.counter += 1 return True

the severity assigned is low, since, as mentioned, this would be a very unusual pattern in user-code.

Patches

fix is tracked in https://github.com/vyperlang/vyper/pull/4644

Workarounds don't have side effects in expressions which construct zero-length bytestrings.

References Are there any links users can visit to find out more?

Other sources

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.dosomesideeffect() 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.

— MITRE

Affected Software

2 affected components
Vyper Vyper<=0.4.2rc1
pip/vyper<=0.4.2rc1

Event History

May 15, 2025
CVE Published
via MITRE·05:24 PM
Data Sourced
via MITRE·05:24 PM
DescriptionWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
May 16, 2025
Advisory Published
via GitHub·02:10 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-47285?

CVE-2025-47285 has been categorized with a high severity due to potential bypass of critical side effects in contract execution.

2

How do I fix CVE-2025-47285?

To fix CVE-2025-47285, upgrade to Vyper version 0.4.2rc2 or later, where the vulnerability is resolved.

3

What versions are affected by CVE-2025-47285?

CVE-2025-47285 affects Vyper versions up to and including 0.4.2rc1.

4

What type of vulnerability is CVE-2025-47285?

CVE-2025-47285 is a logic vulnerability that may allow unwanted side effects due to the skipped evaluation of arguments.

5

Who is affected by CVE-2025-47285?

Developers using Vyper versions up to 0.4.2rc1 in their Ethereum smart contracts are affected by CVE-2025-47285.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203