Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA samsungsemiconductor

CVE-2026-33971: In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service cond

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Samsung Semiconductor Exynos 1280 October 2026; Samsung Semiconductor Exynos 1330 October 2026; Samsung Semiconductor Exynos 1380 October 2026.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Samsung Semiconductor Exynos 1280 October 2026; Samsung Semiconductor Exynos 1330 October 2026; Samsung Semiconductor Exynos 1380 October 2026 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Nov 5, 2026
Updated
Nov 10, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-33971

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for samsung semiconductor records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (samsungsemiconductor). Independent of NVD's CPE analysis and usually ahead of it.

  • Samsung Semiconductor Exynos 1280

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 1330

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 1380

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 1480

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 1580

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 1680

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 2100

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 2200

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 2400

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 2500

    • before October 2026affected · date

  • Samsung Semiconductor Exynos 850

    • before October 2026affected · date

  • Samsung Semiconductor Exynos Modem 5410

    • before October 2026affected · date

Same product

samsung semiconductor: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-48173In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
    39Monitor
  • CVE-2026-69006Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption.
    36Monitor
  • CVE-2026-33969In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of Serv
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-66364Nov 5, 2026 · Continuously sending control‑plane messages causes the baseband to crashes.
    30Monitor
  • ← EarlierCVE-2025-66367Nov 5, 2026 · Improper handling of NAS DLTransport messages may lead to a baseband crash.
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Samsung Semiconductor Exynos 1280October 2026Vendor (CNA)
Samsung Semiconductor Exynos 1330October 2026Vendor (CNA)
Samsung Semiconductor Exynos 1380October 2026Vendor (CNA)
Samsung Semiconductor Exynos 1480October 2026Vendor (CNA)
Samsung Semiconductor Exynos 1580October 2026Vendor (CNA)
Samsung Semiconductor Exynos 1680October 2026Vendor (CNA)
Samsung Semiconductor Exynos 2100October 2026Vendor (CNA)
Samsung Semiconductor Exynos 2200October 2026Vendor (CNA)
Samsung Semiconductor Exynos 2400October 2026Vendor (CNA)
Samsung Semiconductor Exynos 2500October 2026Vendor (CNA)
Samsung Semiconductor Exynos 850October 2026Vendor (CNA)
Samsung Semiconductor Exynos Modem 5410October 2026Vendor (CNA)
Samsung Semiconductor Exynos W1000October 2026Vendor (CNA)
Samsung Semiconductor Exynos W920October 2026Vendor (CNA)
Samsung Semiconductor Exynos W930October 2026Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 10, 2026+6 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. CVSS— → 9.8
  2. Severity— → critical
  3. SSVC exploitation— → none
  4. Exploit maturity— → none
  5. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records