CVE-2026-79104: Missing authorization in Sensor

Published Mar 27, 2026
·
Updated

Chromium: CVE-2026-79104 Missing authorization in Sensor

Other sources

Missing authorization in Sensor in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to obtain sensitive information 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
Google Chrome<152.0.7977.65
Microsoft Edge<152.0.4191.53
Microsoft Edge (Chromium-based)<152.0.4191.53
152.0.4191.53

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 Chromium (Google Chrome) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65
  4. Compensating control

    In Chromium-based browsers (including Microsoft Edge), ensure the browser is up to date since Google Chrome prior to 152.0.7977.65 could allow a remote attacker (with a compromised renderer process) to obtain sensitive information via a crafted HTML page.

Event History

Mar 27, 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:18 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 access does an attacker need to exploit this issue?

The attacker must already have compromised the Chrome renderer process. They can then use a crafted HTML page to obtain sensitive information.

2

Which Chrome versions need to be updated?

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

3

Is this a standalone remote compromise vulnerability?

The available information describes this as requiring a compromised renderer process, so it is not presented as a standalone initial renderer-compromise issue. Its impact is sensitive-information exposure after that prerequisite has been met.

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