# CVE-2025-36939: Memory corruption in Nest

> An authenticated attacker on the Thread network can cause denial of service via crafted MLE packets triggering buffer overflows and assertions in OpenThread.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-x6v7-jjvq-5rr9

## What is CVE-2025-36939?

CVE-2025-36939 is a critical memory corruption vulnerability in Google Nest, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities exist in OpenThread's handling of MLE packets. An authenticated attacker on the same Thread network could send specially crafted packets to cause a denial of service. These issues include triggerable assertion failures and a stack-based buffer overflow.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 3 products.


Products: Google Nest Wifi Point Firmware, Google Nest Wifi Pro Firmware, Google Nest Wifi Router Firmware.

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

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

## Is CVE-2025-36939 being exploited?

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

## Other vulnerabilities in Google Nest

- [CVE-2024-22004](https://insights.sbomify.com/CVE-2024-22004/): Unchecked length in Trusted Application on Google Nest Wifi Pro, leading to out of bounds read (critical 10.0)
- [CVE-2024-22013](https://insights.sbomify.com/CVE-2024-22013/): Missing authorization in Nest Wifi Pro (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-36939 is a critical memory corruption vulnerability in Google Nest, published on 24 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-2025-36939 in the wild and no public exploit code.

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

## Sources

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

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