Skip to main content
VulnerabilityPublished

CVE-2025-66367: Samsung Semiconductor Exynos 850 · Out-of-bounds Read

Affects Samsung Semiconductor Exynos 850Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to July 2026 when convenient.

Data as of 5 Nov 2026, 03:12 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
Patch
Available – fixed in July 2026

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Exynos to July 2026.

Affected software

ProductAffectedFixed in
Samsung SemiconductorExynos 850Affected
  • =0
Fixed in
  • July 2026
Samsung SemiconductorExynos 2100Affected
  • =0
Fixed in
  • July 2026
Samsung SemiconductorExynos 1280Affected
  • =0
Fixed in
  • July 2026
Samsung SemiconductorExynos 2200Affected
  • =0
Fixed in
  • July 2026
Samsung SemiconductorExynos 1330Affected
  • =0
Fixed in
  • July 2026
Samsung SemiconductorExynos 1380Affected
  • =0
Fixed in
  • July 2026

AI-suggested

A fix for this vulnerability was released in July 2026. Users and device manufacturers should apply the official patch to remediate the issue. No additional mitigation steps are indicated.

Description

CVE-2025-66367 is an out-of-bounds read vulnerability (CWE-125) in the Samsung Semiconductor Exynos 850 chipset. It arises from improper handling of NAS DLTransport messages, which may cause the baseband to crash. A fix was released in July 2026.

References

Community reviews

Loading reviews…