nday
CVE-2026-125350

Google Chromium Use-After-Free Vulnerability

Google / Chromium, Chrome

Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 1 of 4 PoC sources: github.

tags weakness typeuse-after-free accessnetworkno authentication required productChrome product typebrowser
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the CNA Chrome and NVD, republishing [email protected]
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
Chrome
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:google:chrome
browser
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:google:chromethe product type of Chrome in nday's product registry
stage
KEV
disclosed
disclosure → PoC
T+0d POC is date-only
cvss
8.8 HIGH v3.1
KEV due date
2026-11-24

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-10T17:20Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
11-10, date only +1 more
ITWexploited
≤ 11-10, inferred from KEV
KEVKEV
11-10, date only

Summary

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)

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.

Event log

2026-11-10date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-11-24. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 6,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-11-10T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-416"
    ],
    "notes": "https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-125350",
    "product": "Chromium",
    "due_date": "2026-11-24",
    "precision": "day",
    "date_added": "2026-11-10",
    "vendor_project": "Google",
    "forensic_triage": "No",
    "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.",
    "vulnerability_name": "Google Chromium Use-After-Free Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-11-10inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

+DISdisclosed

CVE record published by Chrome. CVSS 8.8, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 8336,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-125350",
  "occurred_at": "2026-11-10T17:20:21.161Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-125350",
      "date_added": "2026-11-10"
    },
    "cvss": {
      "source": "adp:CISA-ADP",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-11-09T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-10T17:20:21.161Z",
    "assigner_short_name": "Chrome"
  }
}
2026-11-10date only, from source
+POCpublic PoC

PoC repository on GitHub: ashrafzaryouh/CVE-2026-125350. The date is the repository's creation day.

src github 1452802347 · nday , bulk import · raw
{
  "id": 483195,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/ashrafzaryouh/CVE-2026-125350",
  "occurred_at": "2026-11-10T17:20:21.161Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1452802347",
  "detail": {
    "url": "https://github.com/ashrafzaryouh/CVE-2026-125350",
    "title": "ashrafzaryouh/CVE-2026-125350",
    "precision": "day"
  }
}
2026-11-10date only, from source
+POCpublic PoC

PoC repository on GitHub: Frostmoon39206/CVE-2026-125350-PoC. The date is the repository's creation day.

src github 1453215566 · nday , bulk import · raw
{
  "id": 483196,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/Frostmoon39206/CVE-2026-125350-PoC",
  "occurred_at": "2026-11-10T21:34:01Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1453215566",
  "detail": {
    "url": "https://github.com/Frostmoon39206/CVE-2026-125350-PoC",
    "title": "Frostmoon39206/CVE-2026-125350-PoC",
    "precision": "day"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

  1. 2026-11-12

    Post by @xvonfers on 2026-11-12. Sign in to read it.
  2. 2026-11-12

    Post by @zerodayalpha on 2026-11-12. Sign in to read it.
  3. 2026-11-10

    Post by @sirifu4k1 on 2026-11-10. Sign in to read it.
  4. 2026-11-10

    Post by @im23pds on 2026-11-10. Sign in to read it.
  5. 2026-11-10

    Post by @DailyDarkWeb on 2026-11-10. Sign in to read it.

Sign in to read 5 posts.

sign in to read

Discussion

0 comments

No comments yet.