Security Resilience

CVE-2026-121138

Google Chrome ≤ 157.0.8103.38

Published
03 November 2026
Modified
05 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:H/I:N/A:N
EPSS Score 0.0025 16th 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-121138 is a medium-severity Observable Discrepancy (CWE-203) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Gather Victim Identity Information (T1589); ranked at the 16th 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 IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Observable discrepancy in CORS in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Low)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1589 Gather Victim Identity Information Reconnaissance
Adversaries may gather information about the victim's identity that can be used during targeting.
T1046 Network Service Discovery Discovery
Adversaries may attempt to get a listing of services running on remote hosts and local network infrastructure devices, including those that may be vulnerable to remote software exploitation.
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.
T1595.003 Wordlist Scanning Reconnaissance
Adversaries may iteratively probe infrastructure using brute-forcing and crawling techniques.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-113057Same product: Google Chrome
CVE-2026-110141Same product: Google Chrome
CVE-2026-113300Same product: Google Chrome
CVE-2026-87620Same product: Google Chrome
CVE-2026-87619Same product: Google Chrome
CVE-2026-87459Same product: Google Chrome
CVE-2026-87623Same product: Google Chrome
CVE-2026-112992Same product: Google Chrome
CVE-2026-106336Same product: Google Chrome
CVE-2026-121223Same 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)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Obscures authentication feedback so that success/failure differences are not observable to attackers.

Requires error messages to avoid revealing exploitable details, directly stopping observable response discrepancies.

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 SDLC practices directly prevent observable response discrepancies via consistent error handling and timing.

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.

prevents

Training helps developers recognize that uniform error messages, constant-time comparisons and non-leaking response patterns are security requirements, addressing the common knowledge-gap cases (error-message enumeration, basic auth timing); however, CWE-203 also covers deeper technical instances — cache/power/microarchitectural side channels, TTL and packet-level discrepancies — that exceed what general awareness training reaches, leaving a nameable remainder.

prevents

Secure coding standards can mandate consistent error messages, constant-time comparisons, and uniform response behavior, addressing the application-layer observable discrepancies (different error messages, response timing in auth flows). The remainder is nameable: hardware-level side channels (cache, power consumption, RAPL interfaces), subtle timing differences emerging from complex code paths, and network-level observable differences (TTL, packet behavior) are not caught by coding practice alone, and the clause's mechanism is human practice which is fallible.

prevents

A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so observable discrepancies in delivered code are reduced the way those practices reduce them — but the clause mandates a practice, not a mechanism, and what it catches depends on the rigour of the supplier's implementation, leaving a fallible remainder.

blocks

A.8.5's log-on procedure guidance (items c, d, e) directly blocks user enumeration via error messages and timing discrepancies during authentication, but the control does not address observable discrepancies outside the log-on process such as side-channel attacks or behavioral information leaks.

References