Chrome: Incomplete Cleanup
CVE-2026-95326 is a high-severity incomplete cleanup vulnerability in Chrome from Google, with a CVSS 3.1 base score of 8.4 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 154.0.8037.57 as the first without the flaw, so updating Chrome to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Chrome to 154.0.8037.57 or a later version.
- Read the advisory on chromereleases.googleblog.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Chrome | 154.0.8037.57 up to, but not including, 154.0.8037.57 | 154.0.8037.57 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
Incomplete cleanup in Bluetooth in Google Chrome prior to 154.0.8037.57 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low)
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incomplete Cleanup
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How developers prevent this class of flaw
- Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- issues.chromium.org/issues/533041383Permissions Required
Other vulnerabilities in Chrome
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
Recent Incomplete Cleanup vulnerabilities
- 9.0 Critical severity
- 7.3 High severity
- 9.1 Critical severity
- 8.7 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.