PatchSiren cyber security CVE debrief
CVE-2026-17919 Google CVE debrief
CVE-2026-17919 is a medium-severity vulnerability in Google Chrome on Mac that allows local attackers to perform privilege escalation via physical access to the device. The vulnerability was published on 2026-07-30T01:16:56.090Z and last modified on 2026-10-23T22:10:00.160Z. Defenders responsible for managing Google Chrome on Mac devices should assess exposure and apply the patch (151.0.7922.72) to prevent exploitation. This vulnerability has a CVSS score of 6.8 and is rated as Low by Chromium. It is crucial for defenders to verify and apply the patch, especially in environments where physical access to devices is a concern.
- Vendor
- Product
- Chrome
- CVSS
- MEDIUM 6.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for managing Google Chrome on Mac devices, especially in environments where physical access to devices is a concern, should assess exposure and apply the patch.
Why it matters
CVE-2026-17919 is a medium-severity vulnerability that allows local attackers to perform privilege escalation via physical access to the device. Defenders should prioritize verifying and applying the patch (151.0.7922.72) to prevent exploitation.
- Verify and apply patches to prevent exploitation.
- Restrict physical access to devices to prevent local attackers from exploiting the vulnerability.
- Monitor for suspicious activity related to privilege escalation.
Technical summary
Insufficient policy enforcement in Enterprise in Google Chrome on Mac prior to 151.0.7922.72 allows local attackers to perform privilege escalation via physical access to the device. This vulnerability is a result of inadequate policy enforcement in the Enterprise version of Google Chrome on Mac, which could lead to privilege escalation. The vulnerability has a CVSS score of 6.8 and a Chromium security severity rating of Low. Defenders should prioritize verifying and applying the patch (151.0.7922.72) to prevent local attackers from exploiting this vulnerability.
Defensive priority
Defenders should prioritize verifying and applying the patch (151.0.7922.72) to prevent local attackers from exploiting this vulnerability, especially in environments where physical access to devices is a concern.
Recommended defensive actions
- Verify and apply the patch (151.0.7922.72) to Google Chrome on Mac devices.
- Ensure physical access to devices is restricted to authorized personnel.
- Monitor for any suspicious activity related to privilege escalation.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its CVSS score (6.8) and vector (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The Chromium security severity is rated as Low.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-17919 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-17919
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-17919 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-17919
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html
[email protected] - Release Notes, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/513291747
[email protected] - Permissions Required
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.