ApplicationsHigh 8.8Patch available
CVE-2026-126900
Chrome use-after-free in CSS allows remote code execution in sandbox (pre-157.0.8103.78).
How scary is it?
updated 20 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).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. 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.78
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.
Recommendation, AI-writtenUpdate Chrome to 157.0.8103.78 or later immediately; ensure auto-updates enabled.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 8.8Highscored by CISA
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.42%chance of exploitation in the next 30 daystop 64% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 11 Nov 2026analysed here 14 Nov 2026
Summary
Impact
Remote code execution via crafted HTML/CSS allowing arbitrary code execution inside the browser sandbox.
Triage
Executive summary (AI-written)
CVE-2026-126900 is a high-severity vulnerability identified in Google Chrome that allows for a form of remote code execution due to a use-after-free flaw in the handling of CSS. This vulnerability affects versions of Chrome prior to 157.0.8103.78 and poses a significant risk, particularly in environments where browsing is essential for business operations. While the vulnerability operates within the browser's sandbox, which helps mitigate the impact, its ability to execute arbitrary code means organizations must prioritize patching to prevent potential exploitation. The good news is that a patch has been made available promptly by Google, and organizations are strongly encouraged to update their systems to the latest version. Failure to take action could leave systems exposed to attacks that leverage this vulnerability. Given that Google Chrome is a widely used application across various industries, swift action is essential to safeguard organizational data and maintain cybersecurity posture.
Technical analysis (AI-written)
CVE-2026-126900 is a use-after-free vulnerability located in the CSS handling component of Google Chrome, which under certain conditions could allow an attacker to execute arbitrary code within the browser sandbox. The CVSS score of 8.8 categorizes this vulnerability as high-severity, primarily due to the potential for remote code execution (RCE). Exploitation typically involves the delivery of crafted HTML or CSS content to potentially affected users, who may inadvertently trigger the vulnerability simply by viewing a malicious web page. The exploitation complexity is relatively low, primarily because the attack does not require users to perform any actions beyond opening a malicious website. Given the widespread use of Google Chrome in various sectors, the potential impact of such an exploit could be significant, affecting user privacy and data integrity, even when contained within the browser's sandboxed environment. Mitigation strategies should focus on immediate actions, including ensuring that all instances of Google Chrome are updated to version 157.0.8103.78 or later. Organizations should enable auto-update features for Chrome to facilitate timely application of future patches. Additionally, users should be educated about the risks of visiting untrusted or unknown websites, further reducing the risk of exploitation. In terms of best practices, conducting regular vulnerability assessments and leveraging managed security services to monitor for anomalous behaviors associated with browser exploitation can provide added layers of defense. Lastly, organizations should maintain an up-to-date inventory of software versions and implement a robust patch management process to ensure all critical vulnerabilities are remediated promptly.
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.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Google Chrome | < 157.0.8103.78Vendor 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 < 157.0.8103.78
- Chromium (related builds)
Fix and mitigation
Action required
Patch when possible
WAF and other mitigations
Can a WAF block it? No. The vulnerability is a use-after-free bug in CSS processing, which can be triggered by malicious web content loaded via HTTP requests. The malicious input looks like normal web content, so a web application firewall cannot reliably distinguish it from legitimate requests.
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
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 12 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 11 Nov 2026Published
- 12 Nov 2026CISA SSVC assessment: exploitation nonesame day later
- 13 Nov 2026CVE record last updated1 day later
- 14 Nov 2026Analysed by vulneraibility.com2 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-126900 being exploited?
Not confirmed. CVE-2026-126900 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-126900?
CVE-2026-126900 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-126900?
Yes. A fix has been recorded for CVE-2026-126900. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-126900 affect?
CVE-2026-126900 affects Google Chrome < 157.0.8103.78, Chromium (related builds). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-126900?
Update Chrome to 157.0.8103.78 or later immediately; ensure auto-updates enabled.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Other links (2)
- chromereleases.googleblog.com /2026/11/stable-channel-update-for-desktop_01744469280.html
- issues.chromium.org /issues/574409610
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 Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
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.