LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20972: Improper Export of Android Application Components in UwbTest prior to SMR Jan-2026 Release 1 allows local a...

Improper Export of Android Application Components in UwbTest prior to SMR Jan-2026 Release 1 allows local attackers to enable UWB.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-20972 is a Samsung Mobile issue where a testing component related to UWB may be exposed incorrectly. A local attacker with low privileges could enable UWB on affected devices. Business impact appears limited, but it may matter for environments with strict wireless, proximity, or device-control policies.

Executive priority

Treat as a normal-priority mobile security update, with higher urgency for regulated or high-security fleets that restrict UWB. It does not indicate remote takeover or known exploitation based on the provided sources.

Technical view

The vulnerability is CWE-926, Improper Export of Android Application Components, in Samsung’s UwbTest before the SMR Jan-2026 Release 1. The CVSS 4.0 score is 4.8, with local attack vector, low complexity, low privileges, no user interaction, and low availability impact. The described effect is enabling UWB.

Likely exposure

Exposure is limited to Samsung Mobile Devices running affected Android 13, 14, 15, or 16 builds before the relevant January 2026 Samsung Mobile Security Release. The attacker must already have local, low-privileged access to the device.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not listed as KEV in the source bundle. The scenario is local misuse of an improperly exported Android component, not remote compromise. Practical risk depends on device fleet composition and whether UWB use is restricted.

Researcher notes

Key missing detail is model-specific affected build information beyond Samsung Mobile Devices and Android 13–16. The advisory names UwbTest and the security boundary issue, but does not provide exploit details. Avoid assuming broader impact than local enabling of UWB.

Mitigation direction

  • Review Samsung’s January 2026 security update guidance for this CVE.
  • Apply the relevant Samsung Mobile Security Release when available for each device model.
  • Prioritize managed devices where UWB use is prohibited or tightly controlled.
  • Use MDM policy to restrict wireless features where supported and appropriate.

Validation and detection

  • Inventory Samsung Mobile Devices by model, Android version, and security patch level.
  • Confirm whether devices are on the relevant January 2026 SMR or later.
  • Check Samsung’s advisory for model-specific availability and update status.
  • Verify MDM policy alignment for UWB and nearby-device controls.
Prepared
Confidence
high
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-926: 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-20972 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
4.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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
4.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

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

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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 Android 13, 14, 15, 16affected
Weakness

CWE details

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

CWE-926 · source CWE mapping

Improper Export of Android Application Components

Improper Export of Android Application Components represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.