Skip to main content
VulnerabilityPublished

CVE-2026-33971: Samsung Semiconductor Exynos 850 · Uncontrolled Resource Consumption

Affects Samsung Semiconductor Exynos 850Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to October 2026 soon.

Data as of 5 Nov 2026, 03:13 UTC

Severity
High

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

Thin evidence

One scorer or none
Patch
Available – fixed in October 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 October 2026.

Affected software

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

AI-suggested

A fix for this vulnerability was released by Samsung Semiconductor in October 2026. Users and administrators should apply the official patch or update provided by the vendor to remediate this issue.

Description

CVE-2026-33971 is a vulnerability in the LTE RRC component of the Samsung Semiconductor Exynos 850 chipset. It involves improper handling of messages received before authentication, which triggers a data abort and results in a denial-of-service (DoS) condition. A fix for this issue was released in October 2026.

References

Community reviews

Loading reviews…