CVE-2018-18920
No exploitation reported by the sources we read.
- Published2018-11-12
- Fixed in0.2.0a33
- WeaknessCWE-119
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
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.execute_bytecode call that triggers computation._stack.values with '"stack": [100, 100, 0]' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed indefinitely without gas being paid."
Timeline
dates in UTC- 2018-11-1202:29CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.2 | < 0.2.0a33 | 0.2.0a33 | OSV |
| 0.2 | ≤ 0.2.0a33 | no fix published | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.2 | = 0.2.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.2 | ≤ 0.2.0-alpha\.33 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update py-evm to 0.2.0a33
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
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- NVDweakness (CWE)CWE-119read 2026-10-23
- FIRST EPSSEPSS score2.9 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2020-06-16
Identifiers
- EUVD-2018-0118same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-vqgp-4jgj-5j64same flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2018-155same flawPyPA Advisory Database · CC-BY-4.0
- PYSEC-2018-96same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2018-11-12
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-vqgp-4jgj-5j64
Frequently asked questions
What is CVE-2018-18920?
Is CVE-2018-18920 actively exploited?
What is the CVSS score for CVE-2018-18920?
Running py-evm? 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-vqgp-4jgj-5j64
- 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