How severe is CVE-2025-36939?

CVE-2025-36939 has a CVSS 4.0 base score of 10.0, rated critical severity.

Is CVE-2025-36939 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-36939?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2025-36939 published?

CVE-2025-36939 was published on 2026-08-24 and last updated on 2026-08-31.

CVE-2025-36939

CVE-2025-36939 is a critical-severity vulnerability with a CVSS 4.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Severity: Critical (CVSS 4.0 base score 10.0)
EPSS exploit prediction: 0% (14th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-121
Published: 2026-08-24
Last modified: 2026-08-31

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.

Frequently asked questions

What is CVE-2025-36939?: 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.
How severe is CVE-2025-36939?: CVE-2025-36939 has a CVSS 4.0 base score of 10.0, rated critical severity.
Is CVE-2025-36939 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-36939?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2025-36939 published?: CVE-2025-36939 was published on 2026-08-24 and last updated on 2026-08-31.

References

https://support.google.com/product-documentation/answer/17072818?hl=en&ref_topic=12974021&sjid=16276349370796658455-NC

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

CVE-2026-12848 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12847 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12846 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12485 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-37541 — Critical (CVSS 10.0): Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_gvret.cpp, the length…
CVE-2026-42996 — Critical (CVSS 10.0): JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of…

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →