CVE-2026-110144 Google CVE debrief

Who should care

Defenders responsible for managing Google Chrome installations, particularly in environments where Chrome is widely used, should assess exposure and apply the patch. IT and security teams should verify that all Chrome instances are updated and monitor for suspicious activity.

Why it matters

CVE-2026-110144 is a High-severity vulnerability in Google Chrome on Windows that could allow local attackers to execute arbitrary code outside the sandbox. Defenders should prioritize patching Chrome, assessing exposure, and monitoring for suspicious activity.

• Potential execution of arbitrary code outside the sandbox by a local attacker.
• Requires verification of Chrome version and application of patches.
• Monitoring for suspicious local program activity is necessary.
• Incident response plans should be reviewed and updated.

Technical summary

The vulnerability, CVE-2026-110144, is caused by incorrect authorization in Mojo in Google Chrome on Windows prior to version 155.0.8059.79. This allows a local attacker to potentially execute arbitrary code outside the sandbox via a local program. The vulnerability's High severity indicates that it could have significant operational impacts if exploited, emphasizing the need for defenders to prioritize patching Chrome, assessing exposure, and monitoring for suspicious activity. The CVE record and source item provide details on the vulnerability, including its High severity and potential impact. However, some information, such as CVSS score and specific affected versions, is not provided. Defenders should focus

Defensive priority

Defenders should prioritize verifying and applying the patch to Google Chrome, ensuring all instances are updated to version 155.0.8059.79 or later, and assess exposure in their environment.

Recommended defensive actions

• Verify and apply the patch to Google Chrome, ensuring all instances are updated to version 155.0.8059.79 or later.
• Assess exposure in the environment, focusing on systems where Chrome is used.
• Monitor for any suspicious local program activity that could be related to this vulnerability.
• Review and update incident response plans to account for potential exploitation.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its High severity and potential impact. However, some information, such as CVSS score and specific affected versions, is not provided.

Sources and references

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.