Security Resilience

CVE-2026-121055

Google Chrome ≤ 157.0.8103.38

Published
03 November 2026
Modified
10 November 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0023 15th percentile
Risk Priority 49 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-121055 is a medium-severity Incomplete Cleanup (CWE-459) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 15th 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 AC-12 (Session Termination) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Incomplete cleanup in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to bypass system access restrictions via a crafted Chrome extension. (Chromium security severity: Low)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1078.003 Local Accounts Stealth
Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-95326Same product: Google Chrome
CVE-2026-106243Same product: Google Chrome
CVE-2026-106375Same product: Google Chrome
CVE-2026-126905Same product: Google Chrome
CVE-2026-126856Same product: Google Chrome
CVE-2026-121204Same product: Google Chrome
CVE-2026-106394Same product: Google Chrome
CVE-2026-113012Same product: Google Chrome
CVE-2026-87446Same product: Google Chrome
CVE-2026-85043Same product: Google Chrome

Affected Assets

google
chrome
≤ 157.0.8103.38

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)
  • V6.4.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Session termination forces explicit release of session-related temporary resources.

Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.

Preventing unintended information transfer through shared resources requires complete cleanup of those resources.

Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.

Mitigating Controls (NIST CSF 2.0)

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

PR.PS-06 mostly match
blocks

Secure-development practices and coding standards normally require proper resource release and cleanup.

ID.AM-08 partial match
blocks

Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.

PR.DS-10 partial match
blocks

Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.

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

A.8.29's source reach (code review, static analysis) catches the bulk of CWE-459 instances — unclosed streams, missing finally blocks, and leftover temp files are well-detected code patterns — but a nameable remainder of subtle cases (cleanup dependent on specific error paths, alternate data streams, conditions only observable at runtime) escapes automated detection and requires deeper analysis or specific runtime triggering.

prevents

Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like incomplete cleanup in delivered code the way those practices do, at `partial` -- the same reading that graded A.8.30 -> CWE-134 `partial` and that sits at the clause's declared ceiling.

finds

Change-management processes may require cleanup verification, but the control itself does not address the weakness.

References