# CVE-2025-8192: Race condition in AndroidTV TvSettings

> A race condition in Android TV Settings allows attackers to launch arbitrary activities with system privileges, enabling privilege escalation and code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 31 Jul 2025
- **Also known as:** GHSA-g89h-pfwv-vrq2

## What is CVE-2025-8192?

CVE-2025-8192 is a medium-severity vulnerability in Android TV, published on 31 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There exists a TOCTOU race condition in TvSettings AppRestrictionsFragment.java that lead to start of attacker supplied activity in Settings’ context, i.e. system-uid context, thus lead to launchAnyWhere. The core idea is to utilize the time window between the check of Intent and the use to Intent to change the target component’s state, thus bypass the original security sanitize function.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2025-8192?


## How do I fix CVE-2025-8192?

No fix has been published for CVE-2025-8192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8192 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8192 and fix it if it is affected.

What it is: CVE-2025-8192 is a medium-severity vulnerability in Android TV, published on 31 Jul 2025. 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-2025-8192 in the wild and no public exploit code.

Affected product: Android TV. 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-2025-8192/ (Markdown: https://insights.sbomify.com/CVE-2025-8192/index.md)
```

## Sources

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

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