# CVE-2026-106279: Code injection in Chrome

> A local attacker with compromised renderer access can execute arbitrary code outside the sandbox in Google Chrome on iOS.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106279, ECHO-fc67-0bf9-19ad, GHSA-c453-w7xw-4hq6, MINI-3ffv-p3mj-v63v

## What is CVE-2026-106279?

CVE-2026-106279 is a high-severity code injection vulnerability in Google Chrome, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect reference resolution in Passwords in Google Chrome on on iOS prior to 155.0.8059.39 allowed a local attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a local program. (Chromium security severity: Medium)

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version.

## Is CVE-2026-106279 being exploited?

There is no known exploitation of CVE-2026-106279 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-106279 and fix it if it is affected.

What it is: CVE-2026-106279 is a high-severity code injection vulnerability in Google Chrome, published on 6 Oct 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-106279 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-106279/ (Markdown: https://insights.sbomify.com/CVE-2026-106279/index.md)
```

## Sources

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

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