Skip to main content
VulnerabilityPublished

CVE-2026-121163: Google Chrome · Improper Input Validation

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 157.0.8103.38 when convenient.

Data as of 3 Nov 2026, 21:29 UTC

Severity
Medium

Rated Medium by the CNA (Chrome) · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 157.0.8103.38

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 3 Nov 2026.

What to do

Upgrade Google Chrome to 157.0.8103.38.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=157.0.8103.38 <157.0.8103.38
Fixed in
  • 157.0.8103.38

AI-suggested

Users should update Google Chrome to version 157.0.8103.38 or later, where this vulnerability is fixed. No additional mitigation is required once the update is applied.

Description

An improper input validation vulnerability in Google Chrome prior to version 157.0.8103.38 allows a remote attacker who has compromised the renderer process to execute arbitrary code outside the sandbox via crafted network traffic. The issue has been fixed in version 157.0.8103.38.

References

Community reviews

Loading reviews…