Security Resilience

CVE-2026-121074

Memory Safety in Google Chrome ≤ 157.0.8103.38

Published
03 November 2026
Modified
04 November 2026
Patch / advisory
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0041 36th percentile
Risk Priority 67 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-121074 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Google Chrome. Its CVSS base score is 9.6 (Critical).

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

EU & UK References

Vulnerability Data

Memory corruption in GPU in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-121229Same product: Google Chrome
CVE-2026-49937Same vendor: Google
CVE-2024-7256Same product: Google Chrome
CVE-2023-1230Same product: Google Chrome
CVE-2024-7964Same product: Google Chrome
CVE-2023-1223Same product: Google Chrome
CVE-2026-126917Same product: Google Chrome
CVE-2023-0697Same product: Google Chrome
CVE-2026-58865Same vendor: Google
CVE-2026-58815Same vendor: Google

Affected Assets

google
chrome
≤ 157.0.8103.38

Mitigating Controls

Likely Mitigating Controls

Our mappings. 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-119

Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.

addresses: CWE-119

Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.

addresses: CWE-119

Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.

addresses: CWE-119

Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.

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 in development catches out-of-bounds accesses before release, covering most instances of the weakness.

prevents

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

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-119, a class-level weakness. Rules are authored against its narrower children: CWE-823.

References