CVE-2026-121143VulnerabilityPublished
Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process…
A 0-10 score for how bad the bug is in the worst case. It does not say how common the affected setup is.What do these mean? →—high
- Exploited
- No known exploitation
- Fix
- Fixed in 157.0.8103.38
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 157.0.8103.38.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- High (Chrome)
- Fix
- Fixed in 157.0.8103.38
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High)
What to do
Upgrade to a fixed version: 157.0.8103.38.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Google Chrome
From 157.0.8103.38 · fixed in 157.0.8103.38
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.