Skip to content
Fencer Vulns
high 8.8

CVE-2023-3732 json

Out of bounds memory access in Mojo in Google Chrome prior to 115.0.5790.98 allowed a remote attacker who had compromised the renderer proc…

published 2023-08-01 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-44367

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

Out of bounds memory access in Mojo in Google Chrome prior to 115.0.5790.98 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Patch / fix

  • google chrome 115.0.5790.98
  • chromium Debian 12 115.0.5790.98-1~deb12u1
  • chromium Debian 14, Debian 13 115.0.5790.98-1

debian advisories DEBIAN-CVE-2023-3732

  • chromium openSUSE Tumbleweed 115.0.5790.98-1.1
  • chromium openSUSE Tumbleweed 115.0.5790.102-1.1
  • nodejs-electron openSUSE Tumbleweed 22.3.20-1.1
  • chromium Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 115.0.5790.102-bp155.2.13.1

opensuse advisories openSUSE-SU-2024:13059-1openSUSE-SU-2024:13100-1openSUSE-SU-2024:13125-1openSUSE-SU-2023:0193-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-3732 updated cvss 8.8

chromium-browser: Out of bounds memory access in Mojo

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.