CVE-2026-79085: Missing authorization in Network

Published Jun 10, 2026
·
Updated

Chromium: CVE-2026-79085 Missing authorization in Network

Other sources

Missing authorization in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy 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 Chrome<152.0.7977.65
Google Chrome<152.0.7977.64
152.0.7977.64
Microsoft Edge<152.0.4191.53
Google Chrome<152.0.7977.65
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 Chrome/Chromium (renderer authorization) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65
  4. Upgrade

    Upgrade Microsoft Edge (Chromium-based) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65

Event History

Jun 10, 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 must an attacker achieve before this issue can be exploited?

The attacker must first compromise the Chrome renderer process. After that, a crafted HTML page can be used to bypass the web origin policy.

2

Which Chrome versions need remediation?

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

3

Is this a standalone remote web-page attack?

The available information describes exploitation as requiring a compromised renderer process, so it is not described as a standalone attack from a crafted HTML page alone.

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