Security Resilience

CVE-2026-113216

Google Chrome ≤ 156.0.8078.47

Published
20 October 2026
Modified
03 November 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0035 29th percentile
Risk Priority 64 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-113216 is a high-severity Operation on a Resource after Expiration or Release (CWE-672) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Use of released resource in Navigation in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-121256Same product: Google Chrome
CVE-2026-106310Same product: Google Chrome
CVE-2026-106339Same product: Google Chrome
CVE-2026-95366Same product: Google Chrome
CVE-2026-106320Same product: Google Chrome
CVE-2026-106345Same product: Google Chrome
CVE-2026-13865Same product: Google Chrome
CVE-2026-15108Same product: Google Chrome
CVE-2026-17664Same product: Google Chrome
CVE-2025-1921Same product: Google Chrome

Affected Assets

google
chrome
≤ 156.0.8078.47

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover use-after-free bugs through dynamic analysis or fuzzing.

Engineering principles can require memory-safe constructs or languages that structurally avoid introducing use-after-free.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect use-after-release but does not prevent it at runtime.

prevents

Secure-coding rules require checks that prevent operations on freed or expired objects.

blocks

Change-management processes can introduce or remove resource-lifetime controls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-672, a class-level weakness, and none of its children carries one either.

References