CVE-2026-20983: 
NixOS vulnerability analysis and mitigation

Overview

CVE-2026-20983 is an improper export of Android application components vulnerability in Samsung Dialer that allows local attackers to launch arbitrary activities with Samsung Dialer privileges. It affects Samsung Android versions 14 and 15 prior to SMR Feb-2026 Release 1, and was published on February 4, 2026. The vulnerability carries a CVSS v3.1 base score of 7.8 (High) and a CVSS v4.0 base score of 8.4 (High) (Samsung Security, Feedly).

Technical details

The root cause is improper export of Android application components (CWE-926) within the Samsung Dialer application, which exposes internal activities to other applications on the device without adequate access controls. A local attacker with low privileges can send crafted intents to the improperly exported component, causing the Dialer to launch arbitrary activities under its own elevated privilege context. No user interaction is required, and the attack complexity is low, making exploitation straightforward for any app installed on the device (Samsung Security, Feedly).

Impact

Successful exploitation allows a low-privileged local attacker to execute arbitrary activities within the Samsung Dialer's privilege context, resulting in high confidentiality, integrity, and availability impact on the vulnerable component. An attacker could access sensitive data handled by the Dialer (e.g., call logs, contacts), perform unauthorized operations, or potentially execute malicious code under Dialer's permissions. The scope is limited to the device itself, with no lateral movement to other networked systems, but the compromise of a privileged system application represents a significant risk to device security (Feedly).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of publication (Feedly). The EPSS score is approximately 0.005%, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been reported.

Exploitation steps

  1. Reconnaissance: Identify a target Samsung device running Android 14 or 15 with an SMR release prior to Feb-2026 Release 1, where Samsung Dialer is installed (default on Samsung devices).
  2. Install malicious app: Deploy a malicious application on the device (e.g., via sideloading or a low-privilege app install), which requires only standard user-level access.
  3. Enumerate exported components: Use Android tooling (e.g., adb shell dumpsys package com.samsung.android.dialer) or static analysis of the Dialer APK to identify improperly exported Activity components.
  4. Craft malicious intent: Construct an explicit Android Intent targeting the exported Dialer activity, optionally including extra data or action parameters to influence the launched activity's behavior.
  5. Launch arbitrary activity: Invoke startActivity() from the malicious app with the crafted intent, causing Samsung Dialer to launch the targeted activity under its own elevated privileges, granting the attacker access to Dialer-privileged operations and data (Samsung Security, Feedly).

Indicators of compromise

  • Logs: Android system logs (logcat) showing unexpected startActivity calls originating from a third-party application targeting com.samsung.android.dialer components; entries indicating activity launches from unusual calling packages.
  • Process/Application Behavior: Unexpected Dialer UI appearing without user initiation; Dialer performing actions (e.g., initiating calls, accessing contacts) not triggered by the user.
  • File System: Presence of unknown or suspicious APKs with permissions to interact with Dialer components; newly installed apps with no legitimate need to invoke Dialer activities.
  • Network: Unusual outbound connections from the Dialer process if a malicious payload leverages Dialer privileges for data exfiltration.

Mitigation and workarounds

Samsung has released a patch in SMR Feb-2026 Release 1 for devices running Android 13, 14, and 15. Users should immediately apply the February 2026 Samsung security update via Settings > Software Update > Download and Install. As interim controls, restrict installation of applications from unknown sources and limit physical access to devices. No configuration-based workaround is available that fully mitigates the vulnerability without applying the patch (Samsung Security).

Community reactions

Coverage of CVE-2026-20983 has been limited to vulnerability aggregator sites and security news outlets. SammyFans reported on the February 2026 Samsung security update that includes this fix (SammyFans). A brief technical summary was published by Infinit Security (Infinit Security). No significant researcher commentary or broader community discussion has been observed.

Additional resources


Source: This report was generated using AI

Related NixOS vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-116199CRITICAL9.2
  • NixOS logoNixOS
  • cpe:2.3:a:snipeitapp:snipe-it
NoYesOct 25, 2026
CVE-2026-116201HIGH8.7
  • NixOS logoNixOS
  • cpe:2.3:a:snipeitapp:snipe-it
NoYesOct 25, 2026
CVE-2026-116200HIGH8.2
  • NixOS logoNixOS
  • cpe:2.3:a:snipeitapp:snipe-it
NoYesOct 25, 2026
CVE-2026-2270MEDIUM5.9
  • NixOS logoNixOS
  • kubernetes
NoYesOct 26, 2026
CVE-2026-76654MEDIUM5.8
  • NixOS logoNixOS
  • cpe:2.3:a:kubernetes:kubernetes
NoYesOct 26, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management