CVE-2026-95315: Use after free in Aura in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute

Q: How do I fix CVE-2026-95315?

chrome: upgrade to 154.0.8037.57. Exact commands for each OS are on this page.

Q: Is CVE-2026-95315 being exploited?

CVE-2026-95315 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-95315 affect?

CVE-2026-95315 affects chrome. Severity is high (CVSS 7.8). Use after free in Aura in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)

Routine

HIGH 7.8UPGRADE

CVE-2026-95315 is a high-severity flaw (CVSS 7.8) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Use after free in Aura in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-09-29
Last modified	2026-09-30

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-09-30 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-29 18:17 UTCPublished CVE record published
2026-09-30 16:29 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 154.0.8037.57

Fixed in: 154.0.8037.57

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 154.0.8037.57 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-95315?

chrome: upgrade to 154.0.8037.57. Exact commands for each OS are on this page.

Is CVE-2026-95315 being exploited?

CVE-2026-95315 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-95315 affect?

CVE-2026-95315 affects chrome. Severity is high (CVSS 7.8). Use after free in Aura in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)

How urgent is CVE-2026-95315?

Priority 28/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-113344 HIGH 8.8 UPGRADE Use after free in Performance in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arb
CVE-2026-8510 HIGH 7.5 UPGRADE Integer overflow in Skia in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker who had
CVE-2026-8517 HIGH 8.8 UPGRADE Object lifecycle issue in WebShare in Google Chrome on Mac prior to 148.0.7778.168 allowed a remote attacker w
CVE-2026-8509 HIGH 8.8 UPGRADE Heap buffer overflow in WebML in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute ar
CVE-2026-8524 HIGH 8.8 UPGRADE Out of bounds write in WebAudio in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute

References

← Back to latest CVEs