Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.47% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-95357High confidence
Out of bounds write in GPU in Google Chrome on on Android 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
Within 72 hours
Patch availableCritical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Google Chrome and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-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.
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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 154.0.8037.57-1~deb13u1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian bookwormbookworm · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 154.0.8037.57-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian forkyforky · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 154.0.8037.57-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian sidsid · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 154.0.8037.57-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative 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.
CVE-2026-95357 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitychromium-browser: Out of bounds write in GPU
The vendor explicitly states that these products are not affected by this CVE.
- All currently supported Red Hat products
- Summary
- An out of bounds write flaw was found in the GPU component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=530045332
- Remediation
- No remediation text is recorded.
CVE-2026-95357 · CSAF 2.0 · revision 3 · interimSUSE Product Security TeamCVE-2026-95357
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 GPU in Google Chrome on on Android 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: Critical)
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Critical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.
Patch available01
What, why and how
Out of bounds write in GPU in Google Chrome on on Android 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: Critical)
What
Out of bounds write in GPU in Google Chrome on on Android 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: Critical)
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 GPU in Google Chrome on on Android 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: Critical)
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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- 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:HCommon 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.
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. - Patch available
- Action
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
- 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:55 UTC · CWE-787 · Out-of-bounds Write
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-09-30
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-89212
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-89212 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-89212"}
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html.chrome-cve-admin@google.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0856730748.html
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.chrome-cve-admin@google.com ↗
- Before
- No public exploit
- After
- Public exploit reference
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.SUSE Product Security Team ↗
- Before
- Awaiting fix
- After
- Mitigation available
- 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.CNA ↗
- 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
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- 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.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.CNA ↗
- Before
- Patch available
- After
- Awaiting fix
- 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).CISA ADP ↗
- 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)
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Catalogue recordCVE added to the BlackTree catalogue.Authoritative vendor advisory ↗
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.