Exploited CVEs / Google / CVE-2026-125350

CVE-2026-125350

Google Chromium Use-After-Free Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies must remediate by 2026-11-24; treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Chrome Releases (security updates), linked below.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Senserva AI read on CVE-2026-125350CISA required actionOfficial fix for CVE-2026-125350What the press saysAdmin questions#14 hottest CVE right now

Risk summary

HighCISA KEV
8.8
CVSS v3 base
<1%
EPSS exploit probability
High
Severity
2026-11-10
Added to KEV
2026-11-24
CISA due date

Actively exploited Google Chromium vulnerability, High severity, CVSS v3 8.8. Added to the CISA KEV catalog 2026-11-10.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
The fix ships from the vendor: Chrome Releases (security updates).
Do this now: Federal remediation deadline 2026-11-24; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated November 10, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2026-125350

CVE-2026-125350 is a use-after-free flaw in the XML component of Google Chromium that lets a remote attacker run arbitrary code inside the browser sandbox through a crafted webpage, and CISA confirmed active exploitation when it added the flaw to the KEV catalog on 2026-11-10. Severity is High (CVSS 8.8), and because the bug sits in Chromium itself, exposure extends beyond Chrome to other browsers built on it. Exploitation only requires a user to load a malicious page, and no ransomware use has been reported so far.

Do this: Inventory every Chromium-based browser in your environment (Chrome, plus any other browsers built on Chromium) and push the vendor's patched build to all of them today, prioritizing user endpoints that browse the open web.

AI-generated from public data, 2026-11-11. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-125350

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2026-125350

Published
2026-11-10
Last revised
2026-11-10
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

CISA confirmed active exploitation of CVE-2026-125350 on 2026-11-10.

  • 2026-11-10 added to the CISA KEV catalog by CISA
  • 2026-11-11 EPSS first scored at 0.0%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal remediation due date: 2026-11-24.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Official fix for CVE-2026-125350

The authoritative fix and affected-version list are published by the vendor. Find the Chromium advisory on Chrome Releases (security updates).

Chrome Releases (security updates)CISA KEV entry

Common questions about CVE-2026-125350

Is CVE-2026-125350 actively exploited?

Yes. CVE-2026-125350 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-11-10, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.

What is the CISA deadline and required action for CVE-2026-125350?

CISA set the federal remediation due date at 2026-11-24. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What fixes CVE-2026-125350?

The authoritative fix is in the vendor advisory: see Chrome Releases (security updates) for the patched Chromium versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-125350?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-125350's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Scope and sources

More exploited Google CVEs
CVE-2026-111497CVE-2026-58704CVE-2026-87491CVE-2026-85046CVE-2026-11645CVE-2026-5281CVE-2026-3910CVE-2026-3909

All Google exploited CVEs on one page: Google vulnerabilities actively exploited.

Authoritative references
CVE recordNVD detailCISA KEV catalogFIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.