CVE-2023-29198

MEDIUMNVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.0Exploit: NoneExposed: 0

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

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using contextIsolation and contextBridge are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. This issue is only exploitable if an API exposed to the main world via contextBridge can return an object or array that contains a javascript object which cannot be serialized, for instance, a canvas rendering context. This would normally result in an exception being thrown Error: object could not be cloned. The app side workaround is to ensure that such a case is not possible. Ensure all values returned from a function exposed over the context bridge are supported. This issue has been fixed in versions 25.0.0-alpha.2, 24.0.1, 23.2.3, and 22.3.6.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
—
EPSS
39.2%
KEV
Not listed

Published

September 6, 2023

Last Modified

November 21, 2024

References (4)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
electron—25.0.0-alpha.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× 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 105 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-29198?
CVE-2023-29198 is a medium vulnerability published on September 6, 2023. Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using contextIsolation and contextBridge are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach…
When was CVE-2023-29198 disclosed?
CVE-2023-29198 was first published in the National Vulnerability Database on September 6, 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-29198 actively exploited?
CVE-2023-29198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-29198?
CVE-2023-29198 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2023-29198?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-29198, 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-29198

Explore →

Is Your Infrastructure Affected by CVE-2023-29198?

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

Start Free Scan →Browse All CVEs