# CVE-2022-42541: Remote code execution


- **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
- **Fix available:** No
- **Published:** 29 Nov 2023
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-7mcq-5qp3-w599

## What is CVE-2022-42541?

CVE-2022-42541 is a critical vulnerability in Google Android, published on 29 Nov 2023. 

### Official description

Remote code execution

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-42541?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2022-42541?

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

## Is CVE-2022-42541 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42541 and fix it if it is affected.

What it is: CVE-2022-42541 is a critical vulnerability in Google Android, published on 29 Nov 2023. 
Exploitation: There is no known exploitation of CVE-2022-42541 in the wild and no public exploit code.

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

## Sources

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

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