CVE-2026-78941: Information leak in Core

Published Mar 31, 2026
·
Updated

Chromium: CVE-2026-78941 Information leak in Core

Other sources

Information leak in Core in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Credit

Google

Affected Software

5 affected componentsFixes available
Google Google Chrome<152.0.7977.65
Google Chrome<152.0.7977.64
152.0.7977.64
Microsoft Edge<152.0.4191.53
Microsoft Edge (Chromium-based)<152.0.4191.53
152.0.4191.53
Google Chrome<152.0.7977.65

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 152.0.7977.64
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 152.0.4191.53
  3. Upgrade

    Upgrade Google Chrome / Chromium to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65
  4. Compensating control

    Ensure Chromium-based browsers (e.g., Microsoft Edge) are updated, since Edge ingests Chromium and addresses this vulnerability via the Chromium update.

Event History

Mar 31, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Aug 25, 2026
CVE Published
via MITRE·08:10 PM
Data Sourced
via MITRE·08:10 PM
DescriptionWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeaknessAffected Software
Aug 28, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What prerequisite does an attacker need to exploit this issue?

The attacker must already have compromised the Chrome renderer process. The issue is then triggered through a crafted HTML page to bypass site isolation and leak information.

2

Which Chrome versions are affected?

Google Chrome versions prior to 152.0.7977.65 are affected. Updating to version 152.0.7977.65 or later addresses the affected version range described.

3

Who is realistically exposed to this vulnerability?

Users are exposed when using an affected Chrome version and a renderer compromise has already occurred. The vulnerability is relevant as a post-compromise escape from Chrome's site-isolation boundary rather than as a standalone renderer-compromise issue.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203