Use after free in Aura in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to…
- 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.
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Data gap: No advisory context yet
- Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
- Severity9.3/10CVSS 8.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 91 if added to CISA KEV
- Would score about 86 if CISA's SSVC rates exploitation active
- Would score about 51 if advisories confirm default setups are exposed
CVE-2026-121178 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects Chrome; fixed in 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? →
- 36/100 · provisional
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Use after free in Aura in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code 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
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- 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.
Questions about CVE-2026-121178
Is CVE-2026-121178 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121178?
Chrome: from 157.0.8103.38 before 157.0.8103.38.Source: cve.now feed data
How do I fix CVE-2026-121178?
Upgrade to a fixed version: 157.0.8103.38.Source: cve.now feed data