CVE-2026-121250VulnerabilityPublished 3 Nov 2026

Extensions · Use After Free

Source GCVE Database

Compare

Authoritative record:CVE-2026-121250· High

Not known to be exploited : upgrade to 157.0.8103.38 soon.

Data as of 3 Nov 2026, 22:33 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 157.0.8103.38

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-xpfp-6qvr-gp8j

What to do

Upgrade Chrome and google/chrome to 157.0.8103.38.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=157.0.8103.38 <157.0.8103.38	Fixed in 157.0.8103.38
Googlegoogle/chrome`pkg:deb/google/chrome`Other threats	Affected <157.0.8103.38	Fixed in 157.0.8103.38

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users and administrators should update Google Chrome to version 157.0.8103.38 or later to remediate this vulnerability. Since the fixed version is known, applying this update is the recommended and effective mitigation.

Description

A use-after-free vulnerability exists in the Extensions component of Google Chrome versions prior to 157.0.8103.38. This flaw could allow a remote attacker, using social engineering techniques, to execute arbitrary code outside the browser sandbox by delivering a specially crafted Chrome extension. The vulnerability is classified with high severity by Chromium security.

Impact

An attacker who successfully exploits this vulnerability can execute arbitrary code outside the sandbox environment of Chrome, which may lead to full system compromise depending on the privileges of the user running the browser. The attack vector requires social engineering to trick the user into installing a malicious extension.

Summary

The vulnerability identified as CVE-2026-121250 is a use-after-free issue in the Extensions module of Google Chrome before version 157.0.8103.38. Exploitation requires social engineering to convince a user to install a maliciously crafted extension. Successful exploitation could lead to arbitrary code execution outside the sandbox, potentially compromising the host system. The Chromium project rates this security issue as high severity. No CVSS score or patch links are provided in the data, but the fixed version is explicitly stated as 157.0.8103.38.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 22:33 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats