# CVE-2026-79152: Auth bypass in Chrome

> A local attacker can bypass web origin policy in Google Chrome on Android via a co-installed app due to incorrect authorization in CustomTabs.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-79152, ECHO-5e0f-db27-9421, GHSA-hc64-8gxw-rx5r, MINI-fph4-hq9p-7v4v

## What is CVE-2026-79152?

CVE-2026-79152 is a critical authentication bypass vulnerability in Google Chrome, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect authorization in CustomTabs in Google Chrome on on Android prior to 152.0.7977.65 allowed a local attacker to bypass web origin policy via a co-installed app. (Chromium security severity: Low)

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version.

## Is CVE-2026-79152 being exploited?

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

What it is: CVE-2026-79152 is a critical authentication bypass vulnerability in Google Chrome, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79152 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-79152/ (Markdown: https://insights.sbomify.com/CVE-2026-79152/index.md)
```

## Sources

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

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