LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20974: Improper input validation in data related to network restrictions prior to SMR Jan-2026 Release 1 allows ph...

Improper input validation in data related to network restrictions prior to SMR Jan-2026 Release 1 allows physical attackers to bypass Carrier Relock.

MediumCVSS 5.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-20974 is a Samsung Mobile device issue where a person with physical access could bypass Carrier Relock because network restriction data is not properly validated. This is not described as remotely exploitable. Business urgency is moderate, highest for fleets relying on carrier locks to control device use or resale.

Executive priority

Treat as a targeted mobile fleet hygiene issue, not an emergency internet-facing vulnerability. Prioritize patching devices where carrier restrictions protect business process, financing, custody, or resale controls.

Technical view

Samsung describes improper input validation in data related to network restrictions before SMR Jan-2026 Release 1. The impact is bypass of Carrier Relock by a physical attacker. CVSS 4.0 is 5.2 with physical attack vector, low complexity, no privileges, and high integrity/availability impact to the vulnerable component.

Likely exposure

Exposure appears limited to selected Samsung Mobile Devices running Android 13, 14, 15, or 16 before the relevant January 2026 Samsung Mobile Security Release. Risk depends on device model, patch availability, and whether Carrier Relock is used operationally.

Exploitation context

The provided sources do not report active exploitation, public exploit code, or CISA KEV listing. The attack requires physical access, which reduces broad internet-scale risk but matters for lost, stolen, refurbished, or externally handled devices.

Researcher notes

Evidence is limited to the CVE record and Samsung bulletin reference. No detailed affected model list, proof-of-concept, or exploitation telemetry is included in the provided sources. Avoid assuming impact beyond Carrier Relock bypass and physical-access scenarios.

Mitigation direction

  • Review Samsung’s January 2026 Mobile Security Update for affected models and release timing.
  • Apply SMR Jan-2026 Release 1 or later where Samsung lists support for the device.
  • Prioritize devices using Carrier Relock or exposed to theft, resale, or third-party handling.
  • If updates are unavailable, follow Samsung or carrier guidance for compensating controls.

Validation and detection

  • Inventory Samsung Android 13 through 16 devices in managed fleets.
  • Check each device model against Samsung’s January 2026 security bulletin.
  • Verify installed security patch level or SMR status after updating.
  • Confirm carrier-lock or relock requirements with mobile carrier and device-management teams.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-20: 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 lookup
cve · low confidence lookup

CVE-2026-20974 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.2CVSS 4.0MediumCVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.2Medium
CVSS 4.0 vector shape for CVE-2026-20974Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesSMR Jan-2026 Release in Selected Android 13, 14, 15, 16 devicesaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.