Security Resilience

CVE-2026-118353

Access Control in Google Chrome ≤ 156.0.8078.73

Published
27 October 2026
Modified
03 November 2026
Patch / advisory
CVSS Score v3.1 8.8
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:H/A:H
EPSS Score 0.0021 12th percentile
Risk Priority 63 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-118353 is a high-severity Missing Authorization (CWE-862) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 12th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Missing authorization in Paint in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High)

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-5899Same vendor: Google
CVE-2023-21173Same vendor: Google
CVE-2024-43090Same vendor: Google
CVE-2023-21094Same vendor: Google
CVE-2023-21122Same vendor: Google
CVE-2024-43087Same vendor: Google
CVE-2023-21244Same vendor: Google
CVE-2023-20912Same vendor: Google
CVE-2025-0086Same vendor: Google
CVE-2023-21291Same vendor: Google

Affected Assets

google
chrome
≤ 156.0.8078.73

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover use-after-free bugs through dynamic analysis or fuzzing.

Engineering principles can require memory-safe constructs or languages that structurally avoid introducing use-after-free.

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.

blocks

A.8.3's purpose is to ensure only authorized access, and its guidance directly mandates the authorization checks that CWE-862 describes as missing, so a well-implemented access restriction control fully blocks exploitation of the missing authorization weakness.

finds

By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.

blocks

Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.

finds

Mandating read-only access or proxy execution by an authorized administrator ensures every requested operation is explicitly authorized before it occurs.

blocks

Mandatory authorization checks before allowing modifications ensure that every sensitive action on source code is preceded by an explicit access-control decision.

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-862, a class-level weakness, and none of its children carries one either.

References