CVE-2026-79223: Integer overflow in Chromium

Published Jul 3, 2026
·
Updated

Chromium: CVE-2026-79223 Integer overflow in Chromium

Other sources

Integer overflow in Chromium in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to read memory inside the sandbox via a crafted file. (Chromium security severity: Low)

— NVD

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

Youngjin Ju

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 to a fixed release to a version that resolves this vulnerability.

    Fixed in 152.0.7977.65
  4. Compensating control

    If you use Microsoft Edge (Chromium-based), ensure it is updated since Edge ingests Chromium and addresses the Chromium vulnerability.

Event History

Jul 3, 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 does an attacker need to exploit this issue?

The attacker needs to get Chrome to process a crafted file. The disclosed impact is limited to reading memory inside Chrome's sandbox.

2

Which Chrome versions are affected?

Google Chrome versions before 152.0.7977.65 are affected. Updating to 152.0.7977.65 or later addresses the issue.

3

What can be done if an update cannot be installed immediately?

Avoid opening or processing untrusted files in Chrome until the browser can be updated. The available information does not identify a configuration-based mitigation.

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