Home › Vulnerabilities

Google Chrome Flaw CVE-2026-126912: Update Now

Published November 14, 2026 · Last updated November 14, 2026

Chrome CVE Critical Patch

The short version: CVE-2026-126912 is a critical-severity security flaw in Google Chrome. The National Vulnerability Database (NVD) published it on November 11, 2026, and the score it lists is 9.6 out of 10. When FraudMeNot checked on November 14, 2026, CISA had not added CVE-2026-126912 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

CVE-2026-126912 is a buffer overflow in Skia, the graphics library Google Chrome uses to draw text, shapes and images on screen. Google's CVE record says the bug "allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page." In plain terms, a booby-trapped web page could run an attacker's code on your computer, beyond the protective sandbox that normally boxes in what a web page can touch.

Google fixed it in Chrome 157.0.8103.78, released to the Stable channel on November 11, 2026. It is one of 83 security fixes in that update. Microsoft has since shipped the same fix in its Edge browser, which is built on the same open-source Chromium code.

There is no public report that this flaw has been used in attacks. It is not in the U.S. Cybersecurity and Infrastructure Security Agency's (CISA) Known Exploited Vulnerabilities catalog. CISA's decision data on the CVE record, dated November 12, marks exploitation as "none," automation as "no," and technical impact as "total."

Why the sandbox matters

Chrome runs each web page inside a sandbox, a locked-down process meant to contain any damage if malicious code gets a foothold. Many browser bugs only let an attacker run code inside that box, and they need a second flaw to break out. Google's wording for this one is different: it says code could run "outside the sandbox." That is why CISA's score is so high.

A buffer overflow happens when a program writes more data into a block of memory than the block can hold, spilling into neighboring memory. The CVE record classifies this one as CWE-122, a heap-based buffer overflow. Attackers can sometimes shape that spill to take control of the program.

The attack needs the victim to do something, in this case to open the crafted page. That could mean following a link in an email, a text or a social media post, or landing on a site that has been tampered with.

Severity and who scored it

Google, the CVE Numbering Authority for Chrome, rates the bug "High" under its own Chromium severity scale. Google did not publish a CVSS score.

CISA's Authorized Data Publisher (CISA-ADP) added a CVSS 3.1 score of 9.6 (Critical) to the CVE record on November 13, with vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. That breaks down as reachable over the network, low complexity, no privileges needed, user interaction required, a change in scope (escaping the sandbox), and high impact on confidentiality, integrity and availability. NVD shows the CISA-ADP score as a Secondary source and had not added its own Primary score when we checked; its analysis was still under way. Microsoft's Security Update Guide lists the same 9.6 score for Edge and rates the issue "Important."

The gap between Google's "High" label and CISA's "Critical" score reflects two different scales, not a dispute over the facts.

What else Chrome 157 fixed

Google's release notes list 83 security fixes in Chrome 157, five rated Critical and 78 rated High. The five Critical entries are all use-after-free bugs, a kind of memory error in which a program keeps using memory it has already released:

  • CVE-2026-126885 in ServiceWorker
  • CVE-2026-126895 in CSS
  • CVE-2026-126879 in Layout
  • CVE-2026-126846 in Skia
  • CVE-2026-126911 in Accessibility

Skia and V8, Chrome's JavaScript engine, account for 17 fixes each. Use-after-free is the most common bug type on the list, followed by uninitialized resources and type confusion. Google's own teams reported a majority of the issues; outside researchers include the person credited with CVE-2026-126912, Xinyang Ge, who reported it on October 5, 2026.

Google says access to bug details "may be kept restricted until a majority of users are updated with a fix." The public issue tracker entry for this flaw (569286603) is therefore not a source of extra detail yet.

The fix

Update to a version that contains the fix:

  • Chrome on Windows and Mac: 157.0.8103.78 or 157.0.8103.79
  • Chrome on Linux: 157.0.8103.78
  • Chrome on Android: 157.0.8103.78. Google says Android releases "contain the same security fixes as their corresponding Desktop releases" unless otherwise noted.
  • Chrome Extended Stable (Windows and Mac): 156.0.8078.100. Its November 11 notes list CVE-2026-126912 among 72 security fixes.
  • Microsoft Edge (Chromium-based): 157.0.4341.57, according to Microsoft's Security Update Guide, which explains that Edge "ingests Chromium, which addresses this vulnerability."

Google says the Stable update "will roll out over the coming days/weeks," so a browser may not have it yet even if automatic updates are on. Chrome downloads updates in the background but applies them only after a restart. Opening the About Google Chrome page (Settings, then About Chrome) checks for the update and offers a Relaunch button.

What to do

  • Everyone using Chrome: open the About page, let Chrome update, and relaunch. Confirm the version number is at least the one listed above for your system.
  • Edge users: check that Edge shows 157.0.4341.57 or later under its About page.
  • Android users: update Chrome from Google Play; Google says it will reach devices over several days.
  • IT administrators: push the update to managed desktops rather than waiting for the staged rollout, and confirm that machines have actually restarted the browser. Organizations on Extended Stable should move to 156.0.8078.100.
  • Until you have updated: be wary of unexpected links, since the attack depends on getting you to open a crafted page.

Other browsers built on Chromium are likely to need the same upstream fix. Google and Microsoft have published fixed versions only for Chrome and Edge, so check with the maker of any other Chromium-based browser you use.

Timeline

  • October 5, 2026: Xinyang Ge reports the bug to Google.
  • November 11, 2026: Google releases Chrome 157.0.8103.78/.79 and Extended Stable 156.0.8078.100; the CVE record is published.
  • November 12, 2026: CISA records its exploitation assessment as "none."
  • November 13, 2026: CISA-ADP adds the 9.6 score; Microsoft publishes the Edge fix in its Security Update Guide.

Sources: Google Chrome Releases blog (Stable Channel Update for Desktop, Extended Stable Update for Desktop and Chrome for Android Update, November 11, 2026); the CVE record published by Google, with CISA-ADP data; NVD; Microsoft Security Update Guide.

What the official record says about CVE-2026-126912

The record was filed by google.com. In its own words: "Buffer overflow in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)"

Why Chrome admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). 134c704f-9b21-4f2e-91b3-4a467353bcc0 rated CVE-2026-126912 9.6 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; a user has to take an action, such as opening a file or link. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Chrome running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.

Affected Chrome releases

According to the record, these releases are vulnerable:

  • 157.0.8103.78 up to, but not including, 157.0.8103.78

The type of bug behind CVE-2026-126912

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-122, Heap-based Buffer Overflow. MITRE describes this class of bug as follows: "The product writes past the end of a buffer that was allocated on the heap."

Vendor remediation for CVE-2026-126912

The vendor advisory remediation for operators of Chrome, quoted for this page, is: "Upgrade Google Chrome to 157.0.8103.78 or 157.0.8103.79 (Windows and Mac), 157.0.8103.78 (Linux), or 157.0.8103.78 (Android). Chrome Extended Stable (Windows and Mac) should move to 156.0.8078.100. Microsoft Edge (Chromium-based) should move to 157.0.4341.57 or later, per Microsoft's Security Update Guide. Relaunch the browser so the update applies."

What to do about it

  • Update now: Upgrade Google Chrome to 157.0.8103.78 or 157.0.8103.79 (Windows and Mac), 157.0.8103.78 (Linux), or 157.0.8103.78 (Android). Chrome Extended Stable (Windows and Mac) should move to 156.0.8078.100. Microsoft Edge (Chromium-based) should move to 157.0.4341.57 or later, per Microsoft's Security Update Guide. Relaunch the browser so the update applies.
  • Who should act: IT teams, managed service providers, and developers who run or ship Chrome. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Google (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 11, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-126912. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-126912 record details from CISA and NVD

  • Attack complexity for CVE-2026-126912: low
  • CVE-2026-126912 CVSS scope: changed
  • NVD sub-scores for CVE-2026-126912: exploitability 2.8, impact 6.0.
  • Who mapped the weakness type: the address listed on google.com (Secondary)
  • References in the NVD record: 2.
  • CISA SSVC decision points for CVE-2026-126912 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • November 11, 2026: NVD publishes CVE-2026-126912.
  • November 14, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-126912 is not listed.
  • November 13, 2026: most recent NVD update (record status: Undergoing Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.