TL;DR: Update all Chromium-based browsers to Google Chrome 153.0.8010.36 or later immediately; this vulnerability is actively tracked by CISA under BOD 26-04 and requires prompt patching.
What Is the Flaw?
CVE-2026-87491 is an out-of-bounds write vulnerability (CWE-787) in the V8 JavaScript engine embedded in Google Chrome prior to version 153.0.8010.36. An out-of-bounds write occurs when a program writes data beyond the allocated boundary of a memory buffer, potentially corrupting adjacent memory regions in ways that can be leveraged to redirect program execution.
According to the NVD description, an attacker who controls a crafted HTML page can trigger this memory corruption condition and achieve arbitrary code execution inside the browser sandbox. The Chromium project internally rated this issue as Medium severity; however, the CVSS 3.1 base score calculated by NVD is 8.8 (HIGH), reflecting its network-reachable, low-complexity attack path that requires only a single user interaction — visiting a malicious page.
The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H indicates:
- Network-accessible attack surface — no special network position needed.
- Low attack complexity — no race conditions or unusual preconditions required.
- No privileges required — the attacker needs no existing account or access.
- User interaction required — a victim must visit or be redirected to the attacker-controlled page.
- High impact on confidentiality, integrity, and availability within the affected scope.
Who and What Is Affected?
The vulnerability directly affects Google Chrome prior to version 153.0.8010.36. Because V8 is the shared JavaScript engine at the heart of the Chromium open-source project, CISA notes in its KEV entry that this vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Organizations should evaluate their exposure across all Chromium-based browsers deployed on endpoints, including:
- Google Chrome (all supported platforms)
- Microsoft Edge (Chromium-based versions)
- Opera and other Chromium-derived browsers
Any user, managed device, or unmanaged device that browses to untrusted web content while running an affected browser version is at risk. This includes corporate workstations, developer machines, kiosk systems, and any device where a Chromium-based browser is installed and used to access the internet.
Potential Impact
Successful exploitation allows a remote attacker to execute arbitrary code inside the browser sandbox. While the sandbox provides an important layer of containment, code execution within it is a serious stepping stone that can:
- Enable theft of data accessible within the browser session, including authentication tokens, cookies, and form data.
- Serve as a foundation for chaining with a separate sandbox-escape vulnerability to achieve full operating-system-level compromise.
- Facilitate drive-by download attacks, credential harvesting, or further lateral movement if combined with additional weaknesses.
CISA's inclusion of this CVE in the Known Exploited Vulnerabilities catalog as of 2026-09-09 signals that exploitation in the wild has been confirmed, elevating urgency beyond a standard patching cycle. Federal agencies are bound by CISA's Binding Operational Directive (BOD) 26-04 to remediate KEV entries within prescribed timelines; non-federal organizations are strongly encouraged to follow the same guidance.
The high CVSS score of 8.8 and the low barrier to triggering the vulnerability — a single visit to a malicious page — mean that even users who practice cautious browsing habits can be exposed through malvertising, compromised legitimate sites, or phishing links.
What to Do Now
CISA's required action for this KEV entry directs affected organizations to apply mitigations in accordance with vendor instructions, ensuring compliance with BOD 26-04 guidance and CISA's Forensics Triage Requirements. If mitigations are unavailable, CISA instructs organizations to discontinue use of the affected product. The following steps reflect that guidance:
- Patch immediately. Update all Chromium-based browsers to at least Google Chrome
153.0.8010.36. For Microsoft Edge and other Chromium-derived browsers, apply the corresponding vendor updates as soon as they are released. Consult each vendor's own security advisory for specific version numbers. - Verify deployment across all endpoints. Do not rely solely on auto-update mechanisms. Use endpoint management or software inventory tooling to confirm that every managed device running a Chromium-based browser has received the update.
- Extend scope to unmanaged and BYOD devices. Where possible, enforce browser version policies through endpoint management platforms or network access controls.
- Review CISA BOD 26-04 timelines. Federal agencies must comply with the specific patching deadlines defined in BOD 26-04. Non-federal entities should use those timelines as a risk-based benchmark.
- Conduct forensic triage if warranted. CISA references Forensics Triage Requirements in its KEV entry. Organizations with high-value environments or any indication of suspicious browser activity should consult those requirements and consider reviewing endpoint telemetry for indicators of compromise.
- Monitor vendor advisories. Follow the Google Chrome Releases blog and advisories from Microsoft, Opera, and other Chromium-based browser vendors for further guidance specific to their products.
How External Security Testing Surfaces Exposure
An out-of-bounds write in a browser engine is a client-side vulnerability — it is not directly detectable by scanning a web server or network perimeter in the same way a server-side flaw would be. However, external and internal security testing can still help organizations understand and reduce their exposure:
- Asset and software inventory scanning can identify hosts running outdated browser versions, allowing security teams to prioritize patching efforts before exploitation occurs.
- Vulnerability scanning against endpoint software inventories — particularly when scanner plugins are updated to include CVE-2026-87491 detection logic — can flag unpatched Chromium-based browsers across the environment.
- Web application and phishing simulation testing can assess whether users and email security controls would prevent delivery of a crafted HTML page, reducing the likelihood that a drive-by exploit reaches a vulnerable browser.
- Network egress and DNS filtering controls review can determine whether defensive controls are in place to block access to known malicious domains that might host exploit pages.
Point-in-time external assessments that include browser version enumeration on exposed or managed endpoints provide a snapshot of patching posture and can confirm whether remediation has been fully applied following an advisory like this one.
Sources & further reading: NVD CVE-2026-87491 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: chromereleases.googleblog.com, issues.chromium.org, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does visiting any website put me at risk, or only malicious ones?
According to the NVD description, exploitation requires a user to visit a crafted HTML page. In practice, that page could be hosted on a dedicated malicious site, delivered via a phishing link, or injected through a compromised advertisement on an otherwise legitimate website. Any browsing activity with an unpatched Chromium-based browser carries risk; patching eliminates it.
Does this vulnerability allow a full system takeover?
The NVD description specifies that the attacker achieves arbitrary code execution inside the browser sandbox, not necessarily a full operating-system compromise. The sandbox is a containment boundary designed to limit what browser-level code can do. That said, sandbox-level code execution is serious and can be chained with other vulnerabilities; patching promptly is the correct response.
Are browsers other than Google Chrome affected?
CISA's KEV entry explicitly states that this vulnerability could affect multiple browsers that utilize Chromium, including but not limited to Google Chrome, Microsoft Edge, and Opera. Organizations should check for updated releases from each Chromium-based browser vendor they deploy and apply those updates as they become available.
Why is CISA involved, and does that change the urgency for non-federal organizations?
CISA added CVE-2026-87491 to its Known Exploited Vulnerabilities catalog on 2026-09-09, indicating confirmed exploitation activity. Federal civilian agencies are legally required to remediate KEV entries under BOD 26-04. Non-federal organizations are not legally bound by BOD 26-04 but are strongly encouraged by CISA to treat KEV entries as high-priority patches, as KEV inclusion reflects a real and active threat rather than a theoretical risk.