CVE-2023-2512

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

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

Prior to version v1.20230419.0, the FormData API implementation was subject to an integer overflow. If a FormData instance contained more than 2^31 elements, the forEach() method could end up reading from the wrong location in memory while iterating over elements. This would most likely lead to a segmentation fault, but could theoretically allow arbitrary undefined behavior.

In order for the bug to be exploitable, the process would need to be able to allocate 160GB of RAM. Due to this, the bug was never exploitable on the Cloudflare Workers platform, but could theoretically be exploitable on deployments of workerd running on machines with a huge amount of memory. Moreover, in order to be remotely exploited, an attacker would have to upload a single form-encoded HTTP request of at least tens of gigabytes in size. The application code would then have to use request.formData() to parse the request and formData.forEach() to iterate over this data. Due to these limitations, the exploitation likelihood was considered Low.

A fix that addresses this vulnerability has been released in version v1.20230419.0 and users are encouraged to update to the latest version available.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

May 12, 2023

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
workerd1.20230419.0

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 49× 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.

Showing the most recent 100 of 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-2512?
CVE-2023-2512 is a medium vulnerability published on May 12, 2023. Prior to version v1.20230419.0, the FormData API implementation was subject to an integer overflow. If a FormData instance contained more than 2^31 elements, the forEach() method could end up reading from the wrong location in memory while iterating over elements. This would most likely lead to a…
When was CVE-2023-2512 disclosed?
CVE-2023-2512 was first published in the National Vulnerability Database on May 12, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-2512 actively exploited?
CVE-2023-2512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.1% of all scored CVEs.
What is the CVSS score of CVE-2023-2512?
CVE-2023-2512 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2023-2512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-2512, 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-2512

Explore →

Is Your Infrastructure Affected by CVE-2023-2512?

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