CVE-2023-31146
No exploitation reported by the sources we read.
- Published2023-05-11
- Fixed in0.3.8
- WeaknessCWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, during codegen, the length word of a dynarray is written before the data, which can result in out-of-bounds array access in the case where the dynarray is on both the lhs and rhs of an assignment. The issue can cause data corruption across call frames. The expected behavior is to revert due to out-of-bounds array access. Version 0.3.8 contains a patch for this issue.
Timeline
dates in UTC- 2023-05-1121:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.3 | < 0.3.8 | 0.3.8 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- vyperlang vyperAffected
- = < 0.3.8no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-05-11
Fix
- Update Vyperlang vyper to 0.3.8
Advisories and patches
- github.comPatch
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionnone2025-01-24
- CISA-ADPCVSS 3.19.12025-01-24
- CNACVSS 3.17.5known since 2026-10-23
- NVDCVSS 3.19.1read 2026-10-23
- CISA-ADPweakness (CWE)CWE-7872025-01-24
- CNAweakness (CWE)CWE-787known since 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2023-05-12
Identifiers
- EUVD-2023-0270same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-3p37-3636-q8wvsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2023-77same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
- Published
- 2023-05-11
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-3p37-3636-q8wv
Frequently asked questions
What is CVE-2023-31146?
Is CVE-2023-31146 actively exploited?
What is the CVSS score for CVE-2023-31146?
Running vyper? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-3p37-3636-q8wv
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0