Skip to main content
CVE-2025-12443VulnerabilityPublished

CVE-2025-12443: Google Chrome · Out of bounds read

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium : upgrade to 142.0.7444.59 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 142.0.7444.59
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Google Chrome to 142.0.7444.59.

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =142.0.7444.59
  • <142.0.7444.59
Fixed in
  • 142.0.7444.59

AI-suggested

To mitigate CVE-2025-12443, European organizations should prioritize updating all Chrome installations to version 142.0.7444.59 or later without delay. Enterprises should enforce automated patch management policies to ensure browsers remain current. Network-level controls can be implemented to restrict access to untrusted or suspicious websites, reducing exposure to crafted malicious HTML pages. Security teams should monitor web traffic for unusual patterns indicative of exploitation attempts targeting WebXR components. User awareness training should emphasize the risks of visiting unknown or untrusted websites, especially those offering WebXR content. For organizations deploying WebXR internally, validating and sanitizing WebXR content before distribution can reduce risk. Additionally, employing browser isolation technologies can limit the impact of potential exploits by sandboxing browser sessions. Regular vulnerability scanning and penetration testing focused on browser security can help identify residual risks.

Description

Out of bounds read in WebXR in Google Chrome prior to 142.0.7444.59 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)

References

Community reviews

Loading reviews…