CVE-2023-42443

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). In version 0.3.9 and prior, under certain conditions, the memory used by the builtins raw_call, create_from_blueprint and create_copy_of can be corrupted. For raw_call, the argument buffer of the call can be corrupted, leading to incorrect calldata in the sub-context. For create_from_blueprint and create_copy_of, the buffer for the to-be-deployed bytecode can be corrupted, leading to deploying incorrect bytecode.

Each builtin has conditions that must be fulfilled for the corruption to happen. For raw_call, the data argument of the builtin must be msg.data and the value or gas passed to the builtin must be some complex expression that results in writing to the memory. For create_copy_of, the value or salt passed to the builtin must be some complex expression that results in writing to the memory. For create_from_blueprint, either no constructor parameters should be passed to the builtin or raw_args should be set to True, and the value or salt passed to the builtin must be some complex expression that results in writing to the memory.

As of time of publication, no patched version exists. The issue is still being investigated, and there might be other cases where the corruption might happen. When the builtin is being called from an internal function F, the issue is not present provided that the function calling F wrote to memory before calling F. As a workaround, the complex expressions that are being passed as kwargs to the builtin should be cached in memory prior to the call to the builtin.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
48.7%
KEV
Not listed

Published

September 18, 2023

Last Modified

June 17, 2026

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vyper0.1.0b1 ... 0.3.9 (48 versions)0.3.10

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-08 15:13 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:29 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-01 15:05 UTCEPSS rescore
  12. 2026-06-30 23:21 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-29 14:05 UTCEPSS rescore
  15. 2026-06-28 14:06 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 04:55 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 10:04 UTCOSV refresh
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 14:04 UTCEPSS rescore
Show 61 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-22 14:24 UTCEPSS rescore
  4. 2026-06-22 14:24 UTCEPSS rescore
  5. 2026-06-21 14:55 UTCEPSS rescore
  6. 2026-06-21 14:55 UTCEPSS rescore
  7. 2026-06-21 01:58 UTCEPSS rescore
  8. 2026-06-21 01:58 UTCEPSS rescore
  9. 2026-06-19 19:24 UTCEPSS rescore
  10. 2026-06-19 19:24 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-16 17:51 UTCEPSS rescore
  16. 2026-06-15 17:47 UTCEPSS rescore
  17. 2026-06-15 17:47 UTCEPSS rescore
  18. 2026-06-14 23:16 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-13 22:59 UTCEPSS rescore
  21. 2026-06-12 23:10 UTCEPSS rescore
  22. 2026-06-12 23:10 UTCEPSS rescore
  23. 2026-06-11 13:59 UTCEPSS rescore
  24. 2026-06-11 13:59 UTCEPSS rescore
  25. 2026-06-10 22:17 UTCEPSS rescore
  26. 2026-06-10 13:21 UTCEPSS rescore
  27. 2026-06-10 13:21 UTCEPSS rescore
  28. 2026-06-09 20:47 UTCOSV refresh
  29. 2026-06-08 14:16 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-07 15:23 UTCEPSS rescore
  32. 2026-06-07 15:23 UTCEPSS rescore
  33. 2026-06-06 13:46 UTCEPSS rescore
  34. 2026-06-06 13:46 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 06:09 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 22:29 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-31 00:15 UTCEPSS rescore
  50. 2026-05-29 13:43 UTCEPSS rescore
  51. 2026-05-29 13:43 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-27 13:39 UTCEPSS rescore
  55. 2026-05-27 13:39 UTCEPSS rescore
  56. 2026-05-26 13:43 UTCEPSS rescore
  57. 2026-05-26 13:43 UTCEPSS rescore
  58. 2026-05-26 07:18 UTCEPSS rescore
  59. 2026-05-26 07:18 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-24 17:28 UTCEG score recompute

Frequently asked(5)

What is CVE-2023-42443?
CVE-2023-42443 is a high vulnerability published on September 18, 2023. Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). In version 0.3.9 and prior, under certain conditions, the memory used by the builtins rawcall, createfromblueprint and createcopyof can be corrupted. For rawcall, the argument buffer of the call can be corrupted,…
When was CVE-2023-42443 disclosed?
CVE-2023-42443 was first published in the National Vulnerability Database on September 18, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-42443 actively exploited?
CVE-2023-42443 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 48.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-42443?
CVE-2023-42443 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2023-42443?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-42443, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-42443

Explore →

Is Your Infrastructure Affected by CVE-2023-42443?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.