# CVE-2023-48419: An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in EoP

> An attacker in Wi-Fi range can spy on users and gain elevated privileges on Google Nest Mini devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** No
- **Published:** 2 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-2f47-rm5c-8fr9

## What is CVE-2023-48419?

CVE-2023-48419 is a critical vulnerability in Google Nest Mini, published on 2 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-48419?

It affects 4 products.


Products: Google Home Firmware, Google Home Mini Firmware, Google Nest Audio Firmware, Google Nest Mini Firmware.

## How do I fix CVE-2023-48419?

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

## Is CVE-2023-48419 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48419 and fix it if it is affected.

What it is: CVE-2023-48419 is a critical vulnerability in Google Nest Mini, published on 2 Jan 2024. 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-2023-48419 in the wild and no public exploit code.

Affected product: Google Nest Mini. 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-2023-48419/ (Markdown: https://insights.sbomify.com/CVE-2023-48419/index.md)
```

## Sources

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

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