CVE-2026-79004: Out of bounds read in Media

Published Jul 19, 2026
·
Updated

Chromium: CVE-2026-79004 Out of bounds read in Media

Other sources

Out of bounds read in Media in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox 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-based browsers (Edge/Chromium ingest) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65

Event History

Jul 19, 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

Which Chrome versions are affected?

Google Chrome versions prior to 152.0.7977.65 are affected.

2

What does an attacker need to exploit this issue?

The attacker must first compromise the Chrome renderer process. They can then use a crafted HTML page to trigger an out-of-bounds read and access memory outside the sandbox.

3

Does visiting a crafted page alone exploit the vulnerability?

The provided information states that the renderer process must already be compromised. It does not describe exploitation through page content alone without that prerequisite.

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