EM-20261103-WKG2
VulnerabilityCritical severity
Critical Google Chrome Vulnerability (CVE-2026-121030)
CVE-2026-121030
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 03 20:42 UTCC41 Red Hat Security Data
- Page Born
- Nov 03 21:17 UTCsecond source joined
- Last Signal
- Nov 03 21:17 UTC33 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 28 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 03 21:17 UTCC6 NVD published
- Scored: reachedNov 03 21:17 UTCCVSS 9.6 · EPSS 0.4%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 03 20:42 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-121030 (CVSS 9.6) (opens source in a new tab) Incorrect authorization in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chro… Crit severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-121030 (moderate) (opens source in a new tab) chromium-browser: Incorrect authorization in DevTools Med severityVendorC41 Red Hat Security Data