High 8.8In CISA KEVPatch available
CVE-2026-125350
Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:R).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
5 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- Yes
Attacks seen in the wild3
CISA lists it as exploited in the wild.
- Yes
On CISA's exploited list (since 10 Nov 2026)3
CISA deadline for US federal agencies: 24 Nov 2026.
Scare-o-meter
Drop everything
Attackers are already on it. Patch now.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Google Chrome in an affected version< 157.0.8103.50
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
A person takes an action, such as opening a link or a file
CVSS user interaction: required (UI:R). A victim must click, open or otherwise cooperate.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…
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.
CISA's required action for this KEV entry, due 24 Nov 2026 for US federal agencies.
Source 3
- CVSS
- 8.8Highscored by CISA
- Exploited in the wild
- Yes, in CISA KEV since 10 Nov 2026CISA deadline for US federal agencies: 24 Nov 2026unvetted proof-of-concept code on github
- EPSS
- 1.9%chance of exploitation in the next 30 daystop 20% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 10 Nov 2026analysed here 21 Nov 2026
Do first. 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. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Google Chrome | < 157.0.8103.50Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- google:chrome
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack is delivered via a crafted HTML page loaded in the browser, which looks like a normal web page to a web application firewall. The malicious input is embedded in the page content, so it cannot be reliably distinguished from legitimate web traffic by a WAF.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 10 Nov 2026.
- CISA due date
- 24 Nov 2026, the remediation deadline for US federal agencies
- CISA 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.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 5 GitHub proofs of concept
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 9 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- Frostmoon39206/CVE-2026-125350-PoC5 stars
- TJT001/CVE-2026-125350-PoC1 stars
- ashrafzaryouh/CVE-2026-1253500 stars
- al4n4n/CVE-2026-1253500 stars
and 1 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 9 Nov 2026CISA SSVC assessment: exploitation active
- 10 Nov 2026Added to CISA KEV (exploited in the wild)1 day later
- 10 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
- 10 Nov 2026Published1 day later
- 11 Nov 2026CVE record last updatedsame day later
- 21 Nov 2026Analysed by vulneraibility.com10 days later
- 24 Nov 2026CISA remediation due date (US federal agencies)3 days later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2026-125350 being exploited?
Yes. CVE-2026-125350 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-125350?
CVE-2026-125350 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-125350?
Yes. A fix has been recorded for CVE-2026-125350. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-125350 affect?
CVE-2026-125350 affects google:chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Other links (3)
- chromereleases.googleblog.com /2026/11/stable-channel-update-for-desktop_018223192.html
- issues.chromium.org /issues/582442907
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-125350
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.