BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-95331High confidence

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page

Google · Chrome

9.6CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 27 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google Chrome and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 27 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.154.0.8037.57-1~deb13u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.154.0.8037.57-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.154.0.8037.57-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.154.0.8037.57-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-95331 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitychromium-browser: angle: Out of bounds write in ANGLE
27 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • webkitgtk as a component of Red Hat Enterprise Linux 6
  • webkitgtk-devel as a component of Red Hat Enterprise Linux 6
  • webkitgtk-doc as a component of Red Hat Enterprise Linux 6
  • webkitgtk.src as a component of Red Hat Enterprise Linux 6
  • libwebkit2gtk as a component of Red Hat Enterprise Linux 7
  • webkitgtk3 as a component of Red Hat Enterprise Linux 7
  • webkitgtk3-devel as a component of Red Hat Enterprise Linux 7
  • webkitgtk3-doc as a component of Red Hat Enterprise Linux 7
  • webkitgtk3.src as a component of Red Hat Enterprise Linux 7
  • webkitgtk4 as a component of Red Hat Enterprise Linux 7
  • webkitgtk4-devel as a component of Red Hat Enterprise Linux 7
  • webkitgtk4-doc as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in chromium-browser. An out-of-bounds write vulnerability in the Almost Native Graphics Layer Engine (ANGLE) component may allow a remote attacker to execute arbitrary code outside the browser sandbox. By convincing a user to visit a specially crafted web page, an attacker can corrupt memory and bypass security boundaries to compromise the host system.
Remediation
Affected
CVE-2026-95331 · CSAF 2.0 · revision 3 · interimSUSE Product Security TeamCVE-2026-95331
2 recommended

The vendor recommends these product versions as the target state.

  • chromedriver-154.0.8037.57-1.1 as component of openSUSE Tumbleweed
  • chromium-154.0.8037.57-1.1 as component of openSUSE Tumbleweed
Summary
Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-89251

No EUVD known-exploited evidence

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.6 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 27 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

What

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Write → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-89251Official EUVD mapping

Out of bounds write in ANGLE in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Official EUVD record ↗
BSI · German · WID-SEC-2026-3514Google Chrome / Microsoft Edge: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Chrome / Microsoft Edge ausnutzen, um möglicherweise beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, Spoofing-Angriffe durchzuführen oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1213Multiples vulnérabilités dans Google Chrome

d?id=CVE-2026-95322 Référence CVE CVE-2026-95323 https://www.cve.org/CVERecord?id=CVE-2026-95323 Référence CVE CVE-2026-95324 https://www.cve.org/CVERecord?id=CVE-2026-95324 Référence CVE CVE-2026-95325 https://www.cve.org/CVERecord?id=CVE-2026-95325 Référence CVE CVE-2026-95326 https://www.cve.org/CVERecord?id=CVE-2026-95326 Référence CVE CVE-2026-95327 https://www.cve.org/CVERecord?id=CVE-2026-95327 Référence CVE CVE-2026-95328 https://www.cve.org/CVERecord?id=CVE-2026-95328 Référence CVE CVE-2026-95329 https://www.cve.org/CVERecord?id=CVE-2026-95329 Référence CVE CVE-2026-95330 https://www.cve.org/CVERecord?id=CVE-2026-95330 Référence CVE CVE-2026-95331 https://www.cve.org/CVERecord?id=CVE-2026-95331 Référence CVE CVE-2026-95332 https://www.cve.org/CVERecord?id=CVE-2026-95332 Référence CVE CVE-2026-95333 https://www.cve.org/CVERecord?id=CVE-2026-95333 Référence CVE CVE-2026-95334 https://www.cve.org/CVERecord?id=CVE-2026-95334 Référence CVE CVE-2026-95335 https://www.cve.org/CVERecord?id=CVE-2026-95335 Référence CVE CVE-2026-95336 https://www.cve.org/CVERecord?id=CVE-2026-95336 Référence CVE CVE-2026-95337 https://www.cve.org/CVERecord?id=CVE-2026-95337 Référence CVE CVE-2026-95338 https://www.cve.org/CVERecord?id=CVE-2026-95338 Référence CVE CVE-2026-95339 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-036226GoogleのGoogle Chromeにおける境界外書き込みに関する脆弱性

Google Chromeのバージョン154.0.8037.57より前のANGLEにおける境界外書き込みにより、リモートの攻撃者が細工されたHTMLページを通じてサンドボックス外で任意のコードを実行できる可能性がありました。（Chromiumのセキュリティ重大度は中です）

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • Chrome Releases: Stable Channel Update for Desktop →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026Chrome Releases Release updates from the Chrome team Stable Channel Update for Desktop Tuesday, September 22, 2026 The Chrome team is delighted to announce the promotion of Chrome 154 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks. Chrome 154.0.8037.57 (Linux) 154.0.803
04

Evidence and provenance

Published 29 Sept 2026 · Last source change 30 Sept 2026, 03:56 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-30
European sourceENISA EUVD · EUVD-2026-89251
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-95331 to remediation: access.redhat.com/CVE-2026-95331.
    Before
    remediation: access.redhat.com/CVE-2026-95331
    After
    remediation: access.redhat.com/CVE-2026-95331
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    webkitgtk as a component of Red Hat Enterprise Linux 6; webkitgtk-devel as a component of Red Hat Enterprise Linux 6; webkitgtk-doc as a component of Red Hat Enterprise Linux 6; webkitgtk.src as a component of Red Hat Enterprise Linux 6; libwebkit2gtk as a component of Red Hat Enterprise Linux 7; webkitgtk3 as a component of Red Hat Enterprise Linux 7; webkitgtk3-devel as a component of Red Hat Enterprise Linux 7; webkitgtk3-doc as a component of Red Hat Enterprise Linux 7; webkitgtk3.src as a component of Red Hat Enterprise Linux 7; webkitgtk4 as a component of Red Hat Enterprise Linux 7; webkitgtk4-devel as a component of Red Hat Enterprise Linux 7; webkitgtk4-doc as a component of Red Hat Enterprise Linux 7; webkitgtk4-jsc as a component of Red Hat Enterprise Linux 7; webkitgtk4-jsc-devel as a component of Red Hat Enterprise Linux 7; webkitgtk4-plugin-process-gtk2 as a component of Red Hat Enterprise Linux 7; webkitgtk4.src as a component of Red Hat Enterprise Linux 7; webkit2gtk3 as a component of Red Hat Enterprise Linux 8; webkit2gtk3-devel as a component of Red Hat Enterprise Linux 8; webkit2gtk3-jsc as a component of Red Hat Enterprise Linux 8; webkit2gtk3-jsc-devel as a component of Red Hat Enterprise Linux 8; webkit2gtk3-plugin-process-gtk2 as a component of Red Hat Enterprise Linux 8; webkit2gtk3.src as a component of Red Hat Enterprise Linux 8; webkit2gtk3 as a component of Red Hat Enterprise Linux 9; webkit2gtk3-devel as a component of Red Hat Enterprise Linux 9; webkit2gtk3-jsc as a component of Red Hat Enterprise Linux 9; webkit2gtk3-jsc-devel as a component of Red Hat Enterprise Linux 9; webkit2gtk3.src as a component of Red Hat Enterprise Linux 9
    Red Hat Product Security ↗
  3. ENISA EUVD mappingEUVD-2026-89251 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-89251"}
    ENISA EUVD ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html
    chrome-cve-admin@google.com ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
  6. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CISA ADP ↗
  7. CVSS scoreCVSS score changed from not recorded to 9.6 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.6 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H)
    CISA ADP ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: removed patch: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html; removed remediation: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html.
    Before
    patch: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html · remediation: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html
    After
    no authoritative guidance recorded
    CNA ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    Google Chrome desktop releases before the fixed versions in the linked Stable Channel advisory. · Fixed: Google Chrome stable desktop release: 154.0.8037.57 (Linux) 154.0.8037.57/.58 Windows/Mac.
    After
    Chrome: 154.0.8037.57 < 154.0.8037.57 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  10. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  11. SeveritySeverity changed from Medium to Unknown.
    Before
    Medium
    After
    Unknown
    CVE.org ↗
  12. Catalogue recordCVE added to the BlackTree catalogue.
    Authoritative vendor advisory ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2026-89251↗Vendor CSAF · Red Hat Product Security↗SUSE Product Security Team security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-95331 · cve.blacktree.nl