Cyber Resilience

CVE-2026-7992

High

Published: 06 May 2026

Published
06 May 2026
Modified
06 May 2026
KEV Added
Patch
CVSS Score v3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0022 12.8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-7992 is a high-severity Improper Input Validation (CWE-20) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 12.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability details

Insufficient validation of untrusted input in UI in Google Chrome on Linux, ChromeOS prior to 148.0.7778.96 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium…

more

security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Why these techniques?

Browser UI input validation flaw enabling arbitrary code execution on crafted HTML with user gestures directly matches client-side exploitation technique.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-9123Same product: Google Chrome
CVE-2026-7898Same product: Google Chrome
CVE-2026-8000Same product: Google Chrome
CVE-2026-5915Same product: Google Chrome
CVE-2026-9969Same product: Google Chrome
CVE-2026-9117Same product: Google Chrome
CVE-2026-8534Same product: Google Chrome
CVE-2025-12438Same product: Google Chrome
CVE-2025-12907Same product: Google Chrome
CVE-2026-9988Same product: Google Chrome

Affected Assets

google
chrome
≤ 148.0.7778.96

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-20

Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.

addresses: CWE-20

Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.

addresses: CWE-20

Directly implements checks on information inputs to reject invalid data before processing.

addresses: CWE-20

Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.

References