ApplicationsHigh 8.8Patch available
CVE-2026-131005
Use-after-free in Chrome DevTools allows remote code execution via crafted page
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).
- 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< 158.0.8127.36
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 158.0.8127.36 or later across all endpoints immediately.
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.
Major vulnerability. Chrome is widely deployed; an RCE in DevTools can compromise many corporate endpoints and warrants broad IT distribution.
- CVSS
- 8.8Highscored by CISA
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.37%chance of exploitation in the next 30 daystop 69% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 17 Nov 2026analysed here 20 Nov 2026
Summary
Impact
Remote arbitrary code execution inside Chrome sandbox via crafted HTML, enabling code execution on affected endpoints.
Triage
Executive summary (AI-written)
A critical vulnerability has been identified in Google Chrome's DevTools, designated as CVE-2026-131005, which affects versions prior to 158.0.8127.36. This vulnerability has a CVSS score of 8.8, categorizing it as a major threat due to its potential for remote code execution (RCE) through maliciously crafted HTML pages. The implications for businesses are significant; an attacker could exploit this flaw to execute arbitrary code within the Chrome sandbox of affected endpoints, leading to potential data breaches, loss of sensitive information, and unauthorized control over corporate systems. Given the widespread deployment of Google Chrome in corporate environments, the risk associated with this vulnerability mandates immediate action. Organizations must prioritize the update of Chrome across all endpoints to the latest version to mitigate this threat. Failure to act could result in extensive security breaches and operational disruptions, highlighting the importance of maintaining updated software in today’s cybersecurity landscape.
Technical analysis (AI-written)
CVE-2026-131005 is a use-after-free vulnerability located within Chrome's DevTools, which can be exploited by an attacker under specific conditions, primarily through the delivery of a crafted HTML page. The severity, marked by a CVSS score of 8.8, indicates a high probability of exploitation and a significant potential impact on affected systems. The exploit permits remote code execution within the Chrome sandbox, allowing attackers to run arbitrary code as the user of the browser, potentially compromising user data and system integrity. The attack vector for this vulnerability primarily involves social engineering tactics, where a user may be tricked into loading a malicious HTML page. Once the page executes in the Chrome environment, the use-after-free condition can be manipulated to transition control to the attacker. The complexity of the exploit remains moderate, as it requires user interaction to initiate the attack, but the consequences of a successful exploit can lead to a full system compromise. To mitigate the risk posed by CVE-2026-131005, organizations are advised to implement an immediate upgrade to the latest version of Google Chrome (158.0.8127.36 or later). This patch addresses the vulnerability and closes the attack vector. Furthermore, organizations should consider enforcing policies on browser updates, limiting exposure to untrusted HTML content, and conducting security awareness training to reduce the likelihood of user interaction with malicious content. Ongoing monitoring of CVE alerts and threat intelligence related to web application vulnerabilities is essential for proactive defense. Additionally, deploying intrusion detection systems that can flag anomalous behavior in browser activity may help in early detection of exploitation attempts. Finally, evaluating the overall browser security policies in the enterprise, including regular update schedules and vulnerability testing, is vital to maintain a robust security posture against future vulnerabilities.
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 | < 158.0.8127.36Vendor 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 (desktop) < 158.0.8127.36
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The vulnerability is triggered by a crafted web page loaded in the browser, which looks like a normal HTTP request to the web server. The malicious input is part of the page content, so it resembles normal web traffic and cannot be reliably distinguished 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
- 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 17 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 17 Nov 2026CISA SSVC assessment: exploitation none
- 17 Nov 2026Published1 day later
- 18 Nov 2026CVE record last updatedsame day later
- 20 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-131005 being exploited?
Not confirmed. CVE-2026-131005 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-131005?
CVE-2026-131005 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-131005?
Yes. A fix has been recorded for CVE-2026-131005. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-131005 affect?
CVE-2026-131005 affects Google Chrome (desktop) < 158.0.8127.36. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-131005?
Update Chrome to 158.0.8127.36 or later across all endpoints immediately.
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_01699533288.html
- issues.chromium.org /issues/568986689
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.