What it is
CVE-2026-87491 is an unauthenticated vulnerability affecting Google Chrome. Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via...
Vulnerability report
Chrome
Google / Chrome · affected before 153.0.8010.36
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-87491 is an unauthenticated vulnerability affecting Google Chrome. Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via...
Is it exploited?
Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV. Also confirmed by third-party sources.
Who is affected?
Google / Chrome affected before 153.0.8010.36.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CyberInsider
Independent exploitation attestation added to the Previdian record.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CyberInsider First | 2026-09-09 08:00 UTC |
| TheHackerNews | 2026-09-09 09:11 UTC |
| CISA | 2026-09-09 19:20 UTC |
| CVE | 2026-09-09 20:01 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Risk and context
CVSS v3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.3%
Recent mention · NCSC Security Advisories
Google heeft een zeroday-kwetsbaarheid verholpen in de V8 JavaScript engine van Google Chrome. Google meldt dat de kwetsbaarheid met kenmerk CVE-2026-87491 actief wordt misbruikt. Het betreft een out-of-bounds write in de V8-engine van Google Chrome, die voorkomt in versies...
Read full advisoryRecent mention · NCSC Security Advisories
NCSC-2026-0354 [1.00] [M/H] Kwetsbaarheid verholpen in Google ChromeNCSC Security Advisories · 09 Sep 2026
Google heeft een zeroday-kwetsbaarheid verholpen in de V8 JavaScript engine van Google Chrome. Google meldt dat de kwetsbaarheid met kenmerk CVE-2026-87491 actief wordt misbruikt. Het betreft een out-of-bounds write in de V8-engine van Google Chrome, die voorkomt in versies vóór 153.0.8010.36. Een kwaadwillende kan een speciaal vervaardigde HTML-pagina gebruiken om de kwetsbaarheid te activeren en binnen de sandbox willekeurige code uit te voeren. De kwetsbaarheid wordt veroorzaakt door onjuiste bounds checking in het geheugenbeheer van V8, wat kan leiden tot geheugenbeschadiging. Succesvol...
Recent mention · TheHackerNews
Chrome V8 Zero-Day Exploited in the Wild Enables Code Execution Inside SandboxTheHackerNews · 09 Sep 2026
Google on Thursday released updates to patch 230 security vulnerabilities, including one that has come under active exploitation in the wild. The medium-severity vulnerability, assigned the CVE identifier CVE-2026-87491 (CVSS score: N/A), has been described as an out-of-bounds bug in V8, Chrome's JavaScript and WebAssembly engine. "Out-of-bounds write in V8 in Google Chrome prior to
Recent mention · CyberInsider
Google fixes second actively exploited Chrome zero-day in under five daysCyberInsider · 09 Sep 2026
Google has released Chrome 153 to the stable channel with fixes for 230 security vulnerabilities, including a V8 memory corruption flaw that Google says is already being exploited in attacks. The actively exploited vulnerability is tracked as CVE-2026-87491 and is described as an out-of-bounds write in V8, Chrome’s JavaScript and WebAssembly engine. It was reported … The post Google fixes second actively exploited Chrome zero-day in under five days appeared first on CyberInsider.
Recent mention · Google Chrome Releases
Stable Channel Update for DesktopGoogle Chrome Releases · 08 Sep 2026
The Chrome team is delighted to announce the promotion of Chrome 153 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.Chrome 153.0.8010.36 (Linux) 153.0.8010.36/.37 Windows/Mac contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 153.Security Fixes and RewardsNote: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the...
Timeline
Exploitation attested by an external source
Listed in the CISA Known Exploited Vulnerabilities catalog
Exploitation attested by an external source
High-confidence, third-party attested exploitation
Vulnerability disclosed publicly
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-87491
Free JSON includes basic KEV fields{
"cve_id": "CVE-2026-87491",
"confidence": "Confirmed",
"cvss_score": 8.8,
"cvss_estimated": false,
"epss_score": 0.00291,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}