CVE-2026-9882: Integer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to leak cross-...
Integer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Critical)
A flaw in Google Chrome’s ANGLE component could let a malicious web page leak some cross-origin data from users running Chrome before 148.0.7778.216. It requires the user to visit a crafted page. The record shows no KEV listing or cited evidence of active exploitation.
Executive priority
Treat this as a timely browser update issue, not a crisis signal. Patch Chrome promptly because exploitation only requires visiting a malicious page, but current evidence does not show active exploitation or broader product impact.
Technical view
The CVE describes an integer overflow in ANGLE in Google Chrome prior to 148.0.7778.216. Attack vector is network, low complexity, no privileges, user interaction required, with low confidentiality impact only. The source labels Chromium severity Critical, while the supplied CVSS is 4.3 Medium.
Likely exposure
Exposure is likely wherever managed or unmanaged desktop Chrome remains below 148.0.7778.216. The source bundle does not confirm other browsers, mobile platforms, or downstream Chromium products as affected, so those should be validated through their vendors.
Exploitation context
Sources support a browser-based attack requiring a crafted HTML page and user interaction. There is no KEV listing and no provided source evidence of active exploitation. The documented impact is cross-origin data leakage, not code execution, integrity loss, or availability impact.
Researcher notes
The public record is sparse. It identifies ANGLE, integer overflow, crafted HTML, and cross-origin data leakage, but provides no exploit details, no confirmed exploitation, and no named mitigation beyond the fixed Chrome version. Severity metadata is mixed between Critical vendor severity and Medium CVSS.
Mitigation direction
Update Google Chrome to 148.0.7778.216 or later.
Prioritize managed desktop fleets with delayed browser updates.
Check Google Chrome release guidance for any platform-specific instructions.
Use browser management controls to enforce minimum Chrome versions.
Review vendor advisories before assuming fixes for Chromium-derived browsers.
Validation and detection
Inventory Chrome versions across endpoints and compare against 148.0.7778.216.
Confirm update policy compliance in enterprise browser management tooling.
Check whether high-risk users still run older desktop Chrome builds.
Review web proxy or EDR telemetry for outdated Chrome user agents.
Track the Chromium issue for any newly disclosed technical details.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-472: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.