Security readout for executives and security teams
Plain-English summary
OpenThread can mishandle malicious MLE packets from an attacker already on the same Thread network. The reported outcomes include device or service crashes and a stack-based buffer overflow. This could disrupt connected-device operations and may carry broader security impact, but the supplied evidence does not establish successful code execution.
Executive priority
Treat this as an urgent validation and patch-governance issue because the reported flaw includes memory corruption and a critical score. Prioritize environments where Thread-connected devices support physical security, safety, building operations, or other availability-sensitive functions. Do not assume exposure solely from the listed Nest version because its status is ambiguous.
Technical view
The bundle identifies triggerable assertion failures and a CWE-121 stack-based buffer overflow in OpenThread MLE packet handling. It describes an authenticated, same-Thread-network attacker, while the supplied CVSS 4.0 vector reports PR:N and a 10.0 score. That discrepancy and the exact affected-version scope require vendor clarification.
Likely exposure
Exposure requires reachable OpenThread MLE processing from the same Thread network. The bundle names Google Nest version 3.78.518349 but also marks its default status as unaffected. Consequently, the supplied information does not conclusively identify vulnerable Nest models, firmware versions, or other OpenThread-based products.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in KEV. Exploitation requires specially crafted packets delivered on the same Thread network. No evidence provided here establishes Internet-direct reachability, successful code execution, or exploitation beyond denial of service.
Researcher notes
Key evidence gaps include vulnerable OpenThread releases, affected Nest models, patch identifiers, and whether the overflow enables code execution. The source bundle's authenticated-attacker description conflicts with PR:N in the CVSS vector. Researchers should preserve that distinction and avoid expanding the affected-product scope without authoritative vendor confirmation.
Mitigation direction
- Check Google's advisory for confirmed affected models, firmware versions, and remediation guidance.
- Apply vendor-approved firmware or software updates when available.
- Restrict Thread network membership to trusted devices and remove unauthorized participants.
- Monitor Thread-connected devices for unexplained crashes, restarts, or service disruption.
Validation and detection
- Inventory devices and software using OpenThread or Thread networking.
- Record Google Nest models and firmware versions, including any running 3.78.518349.
- Compare inventory against Google's advisory and subsequent vendor updates.
- Review device telemetry for assertion failures, crashes, restarts, or abnormal Thread traffic.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-36939 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Google_DevicesVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://support.google.com/product-documentation/answer/17072818?hl=en&ref_topic=12974021&sjid=16276349370796658455-NCCVE reference, Google_Devices · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.