LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20979: Improper privilege management in Settings prior to SMR Feb-2026 Release 1 allows local attackers to launch...

Improper privilege management in Settings prior to SMR Feb-2026 Release 1 allows local attackers to launch arbitrary activity with Settings privilege.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-20979 is a Samsung Mobile Settings flaw where a local attacker with an app or device access could start arbitrary activities using Settings privileges. This can increase what a low-privileged local attacker can do on affected Samsung Android devices. Samsung addresses it in SMR Feb-2026 Release 1.

Executive priority

Treat as a high-priority mobile fleet update. It is not described as remotely exploitable, but it can let a local low-privileged attacker use Settings privileges. Prioritize Samsung Android 15 and 16 devices that handle sensitive business data.

Technical view

The issue is improper privilege management (CWE-269) in Samsung Settings before SMR Feb-2026 Release 1. CVSS 4.0 is 8.4: local attack vector, low complexity, low privileges, no user interaction, with high confidentiality and integrity impact and low availability impact.

Likely exposure

Organizations with Samsung Mobile Devices on Android 15 or 16 that have not received SMR Feb-2026 Release 1 are the likely exposure group. Exploitation requires local low-privileged access, such as a malicious local app or attacker-controlled device context.

Exploitation context

The provided sources do not report public exploitation, and the CVE is not marked as KEV. The described impact is local privilege misuse: launching arbitrary activities with Settings privilege. No remote exploitation is indicated in the provided data.

Researcher notes

Public detail is limited to Samsung’s advisory and CVE metadata. Do not assume affected models beyond Samsung Mobile Devices covered by the SMR. Key validation is patch-level confirmation against SMR Feb-2026 Release 1. No KEV listing or cited active exploitation is present.

Mitigation direction

  • Apply Samsung SMR Feb-2026 Release 1 or later where available.
  • Prioritize managed Samsung Android 15 and 16 devices.
  • Use MDM compliance rules to require current Samsung security maintenance releases.
  • Limit installation of untrusted apps on affected devices.
  • Check Samsung’s advisory for model-specific update availability.

Validation and detection

  • Inventory Samsung Mobile Devices running Android 15 or 16.
  • Verify each device’s Samsung security patch level includes SMR Feb-2026 Release 1 or later.
  • Confirm MDM reports no noncompliant devices in the affected population.
  • Review Samsung’s February 2026 bulletin for device and release applicability.
  • Track exceptions where carrier or model updates are delayed.
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 · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-20979 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
High
CVSS
8.4 (4.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 4.0 score

8.4High
CVSS 4.0 vector shape for CVE-2026-20979Attack 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:H/VI:H/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 Feb-2026 Release in Android 15, 16affected
Weakness

CWE details

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

CWE-269 · source CWE mapping

Improper Privilege Management

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