# CVE-2026-9123: Memory corruption in Chrome

> A local attacker can execute arbitrary code inside the sandbox via malicious network traffic due to a heap buffer overflow in Chromecast.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** DEBIAN-CVE-2026-9123, ECHO-13d2-5278-fd42, GHSA-q8x9-c3xr-45r5, MINI-5pww-rp53-frfm

## What is CVE-2026-9123?

CVE-2026-9123 is a high-severity memory corruption vulnerability in Google Chrome, published on 20 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap buffer overflow in Chromecast in Google Chrome on Android, Linux, ChromeOS prior to 148.0.7778.179 allowed a local attacker to execute arbitrary code inside a sandbox via malicious network traffic. (Chromium security severity: Medium)

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-9123?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2026-9123?

Upgrade to a fixed version.

## Is CVE-2026-9123 being exploited?

There is no known exploitation of CVE-2026-9123 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9123 and fix it if it is affected.

What it is: CVE-2026-9123 is a high-severity memory corruption vulnerability in Google Chrome, published on 20 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9123 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9123/ (Markdown: https://insights.sbomify.com/CVE-2026-9123/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9123
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9123
- OSV: https://osv.dev/vulnerability/CVE-2026-9123

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9123/
Summaries are generated and may contain mistakes; the official description above is the record.