CVE-2026-7346

chromium-browser: Inappropriate implementation in Tint

Published Apr 28, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
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)

Analysis

AI-generated

Technical impact

Google Chrome’s Tint rendering engine implements an inappropriate bounds check that can be triggered by a specially crafted HTML page. The flaw allows out-of-bounds memory access (CWE‑119, CWE‑131), which may enable an attacker to read or overwrite arbitrary memory on the client’s machine. The Chromium security team has rated this issue as high severity, indicating the potential for significant impact if the memory corruption is leveraged.

Affected Systems

This vulnerability is present in Google Chrome on all platforms where the Tint engine is used, affecting all versions prior to 147.0.7727.138. Administrators should ensure their Chrome installation is updated to at least 147.0.7727.138 or later to mitigate the defect.

Risk and Exploitability

Exploitability requires delivery of a crafted web page, making it a classic drive‑by attack scenario. The CVSS score of 8.1 reflects a high‑severity risk. The EPSS score of < 1% indicates that while exploitation is possible, the probability of real‑world attacks is low, and the vulnerability is currently not in CISA’s KEV catalog. If an attacker can exploit the out-of-bounds access, it could lead to remote code execution or other severe compromises.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Google Chrome to the most recent release that contains the Tint fix
  • Restart Chrome after applying the update to ensure the patched component is loaded
  • Consider disabling or restricting JavaScript execution in untrusted web pages until the patch is applied

Generated by OpenCVE AI on April 30, 2026 at 14:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6239-1 chromium security update
History
Type Values Removed Values Added
First Time appeared Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
Vendors & Products Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-122
Type Values Removed Values Added
Weaknesses CWE-119
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

Type Values Removed Values Added
Title Out‑of‑Bounds Memory Access in Chrome Tint Rendering Engine chromium-browser: Inappropriate implementation in Tint
Weaknesses CWE-131
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
Title Out‑of‑Bounds Memory Access in Chrome Tint Rendering Engine
Weaknesses CWE-122
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Description 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)
References
Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer

  • CWE-131

    Incorrect Calculation of Buffer Size

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Apr 30, 2026, 3:55 AM
Reserved
Apr 28, 2026, 8:02 PM
Status
Analyzed
Published
Apr 28, 2026, 11:16 PM
Modified
Jul 24, 2026, 8:10 AM
Severity
Important
Public date
Apr 28, 2026, 12:00 AM