CVE-2026-106327

chromium-browser: Incorrect authorization in Core

Published Oct 6, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
Incorrect authorization in Core in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted HTML page. (Chromium security severity: High)

Analysis

AI-generated

Technical impact

Google Chrome contains an incorrect authorization flaw that permits a remote attacker, once they have compromised the renderer process, to bypass system access restrictions by serving a crafted HTML page. The defect lies in Core and is designated as a high‑severity issue in Chromium’s assessment. Because the vulnerability allows a compromised renderer to elevate its privileges and access protected system resources, it can lead to unauthorized file reads or writes, potentially exposing sensitive data or enabling further compromise.

Affected Systems

Google Chrome users of any release prior to version 155.0.8059.39 are affected. The flaw is present in Chromium builds that have not received the 155.0.8059.39 update, so all earlier Chrome versions are impacted.

Risk and Exploitability

The CVSS score of 8.3 indicates high severity; the EPSS score is < 1% and the vulnerability remains unlisted in the CISA KEV catalog. Exploitation requires the attacker to have already compromised the renderer process, implying that the vulnerability is most dangerous in situations where malware or a malicious site has already gained control of the browser’s rendering engine. Given the lack of a known public exploit and the need for a pre‑existing compromise, the practical risk is moderate, but the potential for privilege escalation remains significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Chrome stable channel update to version 155.0.8059.39 or later. This patch removes the incorrect authorization logic that permits renderer processes to bypass system access restrictions.
  • Configure Chrome to run renderer processes with the least privileges possible, ensuring they do not possess elevated system permissions.
  • Use operating‑system sandboxing or containerization to fully isolate Chrome processes, limiting the impact of any compromised renderer.

Generated by OpenCVE AI on October 17, 2026 at 08:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4833-1 chromium security update
Debian DSA Debian DSA DSA-6553-1 chromium security update
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H'}

Type Values Removed Values Added
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 6.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}

Type Values Removed Values Added
Title chromium-browser: Incorrect authorization in Core
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Description Incorrect authorization in Core in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted HTML page. (Chromium security severity: High)
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Oct 14, 2026, 3:03 PM
Reserved
Oct 6, 2026, 4:35 PM
Status
Modified
Published
Oct 6, 2026, 7:18 PM
Modified
Oct 14, 2026, 4:17 PM
Severity
Important
Public date
Oct 6, 2026, 6:41 PM