Cyber Resilience

CVE-2026-7346

Memory Safety in Google Chrome ≤ 147.0.7727.138

Memory Safety
Published
28 April 2026
Modified
24 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.1
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:N
EPSS Score 0.0032 25th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-7346 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Google Chrome. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked at the 25th 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-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-7346 stems from an inappropriate implementation in the Tint component of Google Chrome prior to version 147.0.7727.138. This flaw enables a remote attacker to trigger out-of-bounds memory access through a crafted HTML page. The vulnerability aligns with CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) and carries a Chromium security severity rating of High, with a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

A remote attacker without privileges can exploit this issue by luring a user to interact with a malicious website hosting the crafted HTML page, requiring low attack complexity but user participation such as visiting or rendering the page. Exploitation grants high confidentiality and integrity impacts, potentially allowing unauthorized memory reads or writes, while availability remains unaffected.

Mitigation is provided via the Google Chrome stable channel update to version 147.0.7727.138 or later, as detailed in the Chrome Releases blog at https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html and the Chromium issue tracker at https://issues.chromium.org/issues/502206907. Security practitioners should prioritize browser updates to affected systems.

EU & UK References

Vulnerability Data

Inappropriate implementation in Tint in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-119

Related Threats

MITRE ATT&CK Enterprise Techniques

T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-3910Same product: Apple Macos
CVE-2026-10904Same product: Apple Macos
CVE-2026-8545Same product: Apple Macos
CVE-2026-79069Same product: Apple Macos
CVE-2025-14174Same product: Apple Macos
CVE-2012-2034Same product: Apple Macos
CVE-2023-4073Same product: Apple Macos
CVE-2022-2856Same product: Apple Macos
CVE-2014-8439Same product: Apple Macos
CVE-2017-5070Same product: Apple Macos

Affected Assets

google
chrome
≤ 147.0.7727.138

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

SI-10 Information Input Validation partial match

Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.

SI-16 Memory Protection partial match

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

PR.PS-06 partial match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

References