Bug 2477687 (CVE-2026-8519) - CVE-2026-8519 chromium-browser: angle: chromium-browser: Integer overflow in ANGLE
Summary: CVE-2026-8519 chromium-browser: angle: chromium-browser: Integer overflow in ...
Keywords:
Status: NEW
Alias: CVE-2026-8519
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2540719 2477796 2477797 2540720
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-14 21:04 UTC by OSIDB Bzimport
Modified: 2026-11-06 08:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:69098 0 None None None 2026-09-30 20:10:32 UTC
Red Hat Product Errata RHSA-2026:74084 0 None None None 2026-09-30 19:35:05 UTC
Red Hat Product Errata RHSA-2026:89821 0 None None None 2026-10-26 08:30:08 UTC
Red Hat Product Errata RHSA-2026:89822 0 None None None 2026-10-26 08:22:08 UTC
Red Hat Product Errata RHSA-2026:91631 0 None None None 2026-10-28 08:59:20 UTC
Red Hat Product Errata RHSA-2026:92216 0 None None None 2026-10-29 04:45:21 UTC
Red Hat Product Errata RHSA-2026:92339 0 None None None 2026-10-29 10:27:10 UTC
Red Hat Product Errata RHSA-2026:93435 0 None None None 2026-11-02 01:54:21 UTC
Red Hat Product Errata RHSA-2026:95403 0 None None None 2026-11-05 03:04:34 UTC

Description OSIDB Bzimport 2026-05-14 21:04:36 UTC
Integer overflow in ANGLE in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

Comment 3 Jon Orris 2026-09-30 19:35:04 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:74084 https://access.redhat.com/errata/RHSA-2026:74084

Comment 4 Jon Orris 2026-09-30 20:10:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:69098 https://access.redhat.com/errata/RHSA-2026:69098

Comment 5 Jon Orris 2026-10-26 08:22:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:89822 https://access.redhat.com/errata/RHSA-2026:89822

Comment 6 Jon Orris 2026-10-26 08:30:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:89821 https://access.redhat.com/errata/RHSA-2026:89821

Comment 7 Jon Orris 2026-10-28 08:59:19 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:91631 https://access.redhat.com/errata/RHSA-2026:91631

Comment 8 Jon Orris 2026-10-29 04:45:20 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:92216 https://access.redhat.com/errata/RHSA-2026:92216

Comment 9 Jon Orris 2026-10-29 10:27:09 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:92339 https://access.redhat.com/errata/RHSA-2026:92339

Comment 10 Jon Orris 2026-11-02 01:54:20 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:93435 https://access.redhat.com/errata/RHSA-2026:93435

Comment 11 Jon Orris 2026-11-05 03:04:33 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:95403 https://access.redhat.com/errata/RHSA-2026:95403


Note You need to log in before you can comment on or make changes to this bug.